mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: ARM64: linker: Do not put first function at __image_start
Date: Thu, 21 May 2026 10:15:06 +0200	[thread overview]
Message-ID: <4bb90ae2-125e-40d3-9bc4-b685e16fbecd@pengutronix.de> (raw)
In-Reply-To: <20260521080608.3204583-1-s.hauer@pengutronix.de>

Hello Sascha,

On 5/21/26 10:06 AM, Sascha Hauer wrote:
> The very first function in the barebox binary starts at __image_start
> aka _stext, so resolving its name with %pS results in "__image_start"
> instead of the function name. This can be confusing, so add a small
> offset to the first function so that its name resolves properly.
> 
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

This patch confused me a bit at first, so I would suggest adding
following clarification to the commit message:

"""
This is safe to do for barebox proper, because it's always an ELF on
ARM64 and thus there is no special significance to code at the start of
the text segment.
"""

Thanks,
Ahmad

> ---
>  arch/arm/lib64/barebox.lds.S | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/lib64/barebox.lds.S b/arch/arm/lib64/barebox.lds.S
> index bd76a0ca96..1dddd6d1a9 100644
> --- a/arch/arm/lib64/barebox.lds.S
> +++ b/arch/arm/lib64/barebox.lds.S
> @@ -26,6 +26,7 @@ SECTIONS
>  	.text      :
>  	{
>  		_stext = .;
> +		. += 16;
>  		*(.text*)
>  	} :text
>  

-- 
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 |




      reply	other threads:[~2026-05-21 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  8:06 Sascha Hauer
2026-05-21  8:15 ` Ahmad Fatoum [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=4bb90ae2-125e-40d3-9bc4-b685e16fbecd@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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