From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM64: asm: mark __barebox_arm64_head as function
Date: Fri, 2 Dec 2022 08:46:31 +0100 [thread overview]
Message-ID: <20221202074631.GJ29728@pengutronix.de> (raw)
In-Reply-To: <20221125100959.3981619-1-a.fatoum@pengutronix.de>
On Fri, Nov 25, 2022 at 11:09:59AM +0100, Ahmad Fatoum wrote:
> Calling objdump -d on the PBL ELF file will not disassemble the
> instructions comprising __barebox_arm64_head and instead will just
> print a hexdump. This is because we use linker magic to get the section
> in front of the text segment and GAS fails to detect that
> __barebox_arm64_head too is of function type. This is no longer the case
> with ENDPROC as it uses the GAS .type directive to explicitly mark
> a symbol as being a function:
>
> #define ENDPROC(name) \
> .type name, @function; \
> END(name)
>
> This only has effect on the ELF and introduces no functional change for
> the objcopied image.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> arch/arm/cpu/head_64.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
Sascha
>
> diff --git a/arch/arm/cpu/head_64.S b/arch/arm/cpu/head_64.S
> index f934e96c6eaf..398c4d3471e0 100644
> --- a/arch/arm/cpu/head_64.S
> +++ b/arch/arm/cpu/head_64.S
> @@ -30,4 +30,4 @@ ENTRY(__barebox_arm64_head)
> .rept 8
> .word 0x55555555
> .endr
> -END(__barebox_arm64_head)
> +ENDPROC(__barebox_arm64_head)
> --
> 2.30.2
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2022-12-02 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:09 Ahmad Fatoum
2022-12-02 7:46 ` Sascha Hauer [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=20221202074631.GJ29728@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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