public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [FYI] objtool: .export_symbol…: data relocation to !ENDBR: stpcpy
Date: Fri, 2 Aug 2024 11:35:52 +0200	[thread overview]
Message-ID: <20240802093552.GG39708@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240801152836.xOJc9iaY@linutronix.de>

On Thu, Aug 01, 2024 at 05:28:36PM +0200, Sebastian Andrzej Siewior wrote:
> Hi,
> 
> defconfig on x86-64 with gcc-14 I get this:
> | vmlinux.o: warning: objtool: .export_symbol+0x26980: data relocation to !ENDBR: stpcpy+0x0
> 
> objdump ->
> 
> | 0000000000000110 <stpcpy>:
> |  110:   66 66 2e 0f 1f 84 00    data16 cs nopw 0x0(%rax,%rax,1)
> |  117:   00 00 00 00 
> |  11b:   0f 1f 44 00 00          nopl   0x0(%rax,%rax,1)
> |  120:   f3 0f 1e fa             endbr64
> 
> okay, no endbr64 on entry label.
> 
> | $ make lib/string.s
> ->
> |         .type   stpcpy, @function
> | stpcpy:
> |         .p2align 5
> |         endbr64
> | .L30:
> | # lib/string.c:193:  while ((*dest++ = *src++) != '\0')
> |         movzbl  (%rsi), %eax    # MEM[(const char *)src_8 + -1B], _1
> 
> an alignment request after the function label before endbr64 which gets
> expanded into NOP_11+NOP_5.
> I don't see this with gcc-13.
> Reported as https://gcc.gnu.org/PR116174

Fun, thanks for tracking that down!

      reply	other threads:[~2024-08-02  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 15:28 [FYI] objtool: .export_symbol…: data relocation to !ENDBR: stpcpy Sebastian Andrzej Siewior
2024-08-02  9:35 ` Peter Zijlstra [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=20240802093552.GG39708@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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