public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Sergei Trofimovich <slyfox@gentoo.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] elflint: fix undefined 'buffer_left' reference
Date: Mon, 7 Jun 2021 02:38:31 +0300	[thread overview]
Message-ID: <20210606233831.GB17371@altlinux.org> (raw)
In-Reply-To: <20210606225709.2480357-1-slyfox@gentoo.org>

Hi,

On Sun, Jun 06, 2021 at 11:57:09PM +0100, Sergei Trofimovich via Elfutils-devel wrote:
> Link failure is reproducible on gcc-11.1.0 target:
> 
> ```
> $ autoreconf -i -f
> $ ./configure --enable-maintainer-mode --disable-debuginfod \
>     --host=x86_64-pc-linux-gnu \
>     CFLAGS=-march=znver3 \
>     CXXFLAGS=-march=znver3 \
>     LDFLAGS=" "
> $ make
> 
>   CCLD     elflint
> ld: elflint.o: in function `check_attributes':
> elflint.c:(.text+0xdcff): undefined reference to `buffer_left'
> ld: elflint.c:(.text+0xe557): undefined reference to `buffer_left'
> ```
> 
> It happens due to possible external linkage of `buffer_left()`.
> 
> The change forces local linkkage to always use local definition
> (either inline or out-of-line).
> 
> Reported-by: Toralf Förster
> Bug: https://bugs.gentoo.org/794601
> Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

Fixes: e95d1fbb ("elflint: Pull left() in file scope")

> ---
>  src/ChangeLog | 5 +++++
>  src/elflint.c | 2 +-
>  2 files changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/src/ChangeLog b/src/ChangeLog
> index 2c7be185..e030de0d 100644
> --- a/src/ChangeLog
> +++ b/src/ChangeLog
> @@ -1,3 +1,8 @@
> +2021-06-06  Sergei Trofimovich  <slyfox@gentoo.org>
> +
> +	* elflint.c (buffer_left): Mark as 'inline' to avoid external linkage
> +	failure.

Did you mean 'static'?

> +
>  2021-05-12  Dmitry V. Levin  <ldv@altlinux.org>
>  
>  	* elfcompress.c (process_file): Return 1 instead of -1 in case of an
> diff --git a/src/elflint.c b/src/elflint.c
> index 85cc7833..35b40500 100644
> --- a/src/elflint.c
> +++ b/src/elflint.c
> @@ -3434,7 +3434,7 @@ buffer_pos (Elf_Data *data, const unsigned char *p)
>    return p - (const unsigned char *) data->d_buf;
>  }
>  
> -inline size_t
> +static inline size_t
>  buffer_left (Elf_Data *data, const unsigned char *p)
>  {
>    return (const unsigned char *) data->d_buf + data->d_size - p;

I suppose we could simply replace these 'inline' with 'static'
and let the compiler decide whether to inline or not.


-- 
ldv

  reply	other threads:[~2021-06-06 23:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 22:57 Sergei Trofimovich
2021-06-06 23:38 ` Dmitry V. Levin [this message]
2021-06-07 21:37   ` [PATCH v2] " Sergei Trofimovich
2021-06-07 22:10     ` Dmitry V. Levin

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=20210606233831.GB17371@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=slyfox@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).