public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Xi Ruoyao <xry111@xry111.site>, libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>, Wang Xuerui <i@xen0n.name>,
	Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] LoongArch: ldconfig: Ignore EF_LARCH_OBJABI_V1 in shared objects
Date: Mon, 27 Mar 2023 09:44:36 -0400	[thread overview]
Message-ID: <b72544d0-17bd-0867-41c3-60183ed49b4b@redhat.com> (raw)
In-Reply-To: <20230326111334.9920-1-xry111@xry111.site>

On 3/26/23 07:13, Xi Ruoyao via Libc-alpha wrote:
> Binutils 2.40 sets EF_LARCH_OBJABI_V1 for shared objects:
> 
>     $ ld --version | head -n1
>     GNU ld (GNU Binutils) 2.40
>     $ echo 'int dummy;' > dummy.c
>     $ cc dummy.c -shared
>     $ readelf -h a.out | grep Flags
>     Flags:                             0x43, DOUBLE-FLOAT, OBJ-v1
> 
> We need to ignore it in ldconfig or ldconfig will consider all shared
> objects linked by Binutils 2.40 "unsupported".  Maybe we should stop
> setting EF_LARCH_OBJABI_V1 for shared objects, but Binutils 2.40 is
> already released and we cannot change it.
> ---
>  sysdeps/unix/sysv/linux/loongarch/readelflib.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sysdeps/unix/sysv/linux/loongarch/readelflib.c b/sysdeps/unix/sysv/linux/loongarch/readelflib.c
> index bcaff86b36..ceba355959 100644
> --- a/sysdeps/unix/sysv/linux/loongarch/readelflib.c
> +++ b/sysdeps/unix/sysv/linux/loongarch/readelflib.c
> @@ -40,7 +40,7 @@ process_elf_file (const char *file_name, const char *lib, int *flag,
>  
>    ret = process_elf64_file (file_name, lib, flag, isa_level, soname,
>  				file_contents, file_length);
> -  flags = elf64_header->e_flags;
> +  flags = elf64_header->e_flags & ~EF_LARCH_OBJABI_V1;

Are such objects ABI compatible?

Why isn't this handled below via SUPPORTED_ELF_FLAGS?

>  
>    /* LoongArch linkers encode the floating point ABI as part of the ELF headers.  */
>    switch (flags & SUPPORTED_ELF_FLAGS)

-- 
Cheers,
Carlos.


  reply	other threads:[~2023-03-27 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 11:13 Xi Ruoyao
2023-03-27 13:44 ` Carlos O'Donell [this message]
2023-03-27 14:57   ` Xi Ruoyao
2023-03-27 16:54     ` Adhemerval Zanella Netto
2023-03-27 17:46       ` Xi Ruoyao
2023-03-29 13:12       ` Carlos O'Donell

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=b72544d0-17bd-0867-41c3-60183ed49b4b@redhat.com \
    --to=carlos@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=i@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).