From: Michal Marek <mmarek@suse.cz>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: [PATCH] Kbuild: Check for CONFIG_READABLE_ASM when building .s targets
Date: Tue, 07 Oct 2014 15:45:43 +0200 [thread overview]
Message-ID: <5433EE87.2090000@suse.cz> (raw)
In-Reply-To: <20141007122707.GD30146@pd.tnic>
On 2014-10-07 14:27, Borislav Petkov wrote:
> On Tue, Oct 07, 2014 at 02:13:56PM +0200, Michal Marek wrote:
>> This violates the principle of least surprise:
>>
>> make $file.s
>> as -o $file.o $file.s
>>
>> should be equivalent to
>>
>> make $file.o
>
> I know but we need to enable -g for .s targets so that we get the .loc
> annotation (i.e., line numbers) in asm which is very helpful.
>
> But the least surprise principle is a valid point. Maybe we should warn
> about it too when building .s targets...?
>
> Or, maybe I should try to find out whether there's another gcc option
> which adds ".loc" annotations alone...
Such option would be best of course. BTW, do you know about make
$file.lst to produce an 'annotated disassembly'?
>> Why not simply check both READABLE_ASM and DEBUG_INFO? Also, it's more
>> straightforward to print the warning in the top-level Makefile rule than
>> to add a conditional to the generic rule, like this:
>
> The problem here is that we're building a couple of .s targets
> regardless of what the make command contains, like bounds.s and such.
The toplevel Makefile rule (where your patch adds the asm_target=$@
variable) is only used for manual invocation. bounds.s and the like are
handled by Makefile.build directly.
Michal
next prev parent reply other threads:[~2014-10-07 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 15:32 [PATCH] Kbuild: Check for CONFIG_READABLE_ASM when building .s targets Borislav Petkov
2014-10-05 15:58 ` Borislav Petkov
2014-10-07 12:13 ` Michal Marek
2014-10-07 12:27 ` Borislav Petkov
2014-10-07 13:45 ` Michal Marek [this message]
2014-10-07 14:11 ` Borislav Petkov
2014-10-23 19:24 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5433EE87.2090000@suse.cz \
--to=mmarek@suse.cz \
--cc=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox