From: John Reiser <jreiser@BitWagon.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@elte.hu, Jeff Dike <jdike@addtoit.com>,
Sam Ravnborg <sam@ravnborg.org>,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: STT_FUNC for assembler checksum and semaphore ops" in git-x86
Date: Thu, 10 Jan 2008 20:18:08 -0800 [thread overview]
Message-ID: <4786EE00.3050602@BitWagon.com> (raw)
In-Reply-To: <20080111025734.GA6908@one.firstfloor.org>
Andi Kleen wrote:
> On Thu, Jan 10, 2008 at 04:59:52PM -0800, John Reiser wrote:
>
>>Andi Kleen wrote:
>>
>>>But actually checking the default implementation in linkage.h already
>>>implements size: [snip]
>>
>>>Are you sure it doesn't work? Your patch should be not needed. If it's
>>>still wrong then just ENDPROCs() need to be added.
>>
>>The ENDPROCs() were not used everywhere. Some code used just END() instead,
>>while other code used nothing. um/sys-i386/checksum.S didn't #include
>
>
> END() is fine too since it contains .size too:
>
> #ifndef END
> #define END(name) \
> .size name, .-name
> #endif
>
>
>>diff --git a/arch/x86/lib/semaphore_32.S b/arch/x86/lib/semaphore_32.S
>>index 444fba4..e2c6e0d 100644
>>--- a/arch/x86/lib/semaphore_32.S
>>+++ b/arch/x86/lib/semaphore_32.S
>>@@ -49,7 +49,7 @@ ENTRY(__down_failed)
>> ENDFRAME
>> ret
>> CFI_ENDPROC
>>- END(__down_failed)
>>+ ENDPROC(__down_failed)
>
>
> I don't think these change makes sense given the definition of END()
> shown above.
>
> The only change that would make sense is adding END() (or ENDPROC())
> to a function that doesn't have either of them yet.
No. The pseudo op ".type name, @function" appears only in ENDPROC;
it does not appear in END. So changing END to ENDPROC *does* alter
the Elf32_Sym for 'name'. Just END produces STT_NOTYPE; ENDPROC
produces STT_FUNC. A static analysis tool can get the info it wants
much more easily if all subroutines are marked as STT_FUNC.
In theory the tool could sort the symbols, notice the disjoint
coverage of the address space by the .size intervals of consecutive
symbols that are the targets of a CALL instruction, and thus deduce
that ".type foo, @function" *should* have been specified. But this
is a heuristic, and it fails on boundaries where assembly code is
invoked via trap, interrupt, or exception (anything other than CALL).
Instead, specify STT_FUNC for each subroutine in the first place.
That requires .type, which means ENDPROC (not END) from linux/linkage.h.
--
John Reiser, jreiser@BitWagon.com
prev parent reply other threads:[~2008-01-11 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 21:57 STT_FUNC for assembler checksum and semaphore ops" in git-x86 Andi Kleen
2008-01-10 7:42 ` Sam Ravnborg
2008-01-10 16:37 ` John Reiser
2008-01-10 18:02 ` Andi Kleen
2008-01-11 0:59 ` John Reiser
2008-01-11 2:57 ` Andi Kleen
2008-01-11 4:18 ` John Reiser [this message]
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=4786EE00.3050602@BitWagon.com \
--to=jreiser@bitwagon.com \
--cc=andi@firstfloor.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).