From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>, <libc-alpha@sourceware.org>
Subject: Re: x86_64 / i686 no-PIE failures
Date: Fri, 04 Nov 2022 08:12:07 +0100 [thread overview]
Message-ID: <87a6572ny0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208172224050.417173@digraph.polyomino.org.uk> (Joseph Myers's message of "Wed, 17 Aug 2022 22:27:09 +0000")
* Joseph Myers:
> Now that the uchar.h failures with mainline GCC are fixed, other failures
> show up for x86_64 / i686 no-PIE with mainline GCC and binutils (I don't
> know how long these have been there):
>
> /scratch/jmyers/glibc-bot/install/compilers/x86_64-linux-gnu/lib/gcc/x86_64-glibc-linux-gnu/13.0.0/../../../../x86_64-glibc-linux-gnu/bin/ld: /scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-no-pie/glibc/elf/ifuncmain1.o: non-canonical reference to canonical protected function `foo_protected' in /scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-no-pie/glibc/elf/ifuncmod1.so
> /scratch/jmyers/glibc-bot/install/compilers/x86_64-linux-gnu/lib/gcc/x86_64-glibc-linux-gnu/13.0.0/../../../../x86_64-glibc-linux-gnu/bin/ld: failed to set dynamic section sizes: bad value
> collect2: error: ld returned 1 exit status
> ../Rules:238: recipe for target '/scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-no-pie/glibc/elf/ifuncmain1' failed
> make[3]: *** [/scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-no-pie/glibc/elf/ifuncmain1] Error 1
> make[3]: Leaving directory '/scratch/jmyers/glibc-bot/src/glibc/elf'
H.J.,
this test no longer seems valid with current binutils (or current
binutils is broken).
ifuncmain1.o has X86_64_32S and X86_64_PLT32 relocations for
foo_protected, so the main program must contain a PLT stub for
foo_protected. Apparently, ld no longer produces such binaries.
What should we do about this?
Thanks,
Florian
next prev parent reply other threads:[~2022-11-04 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 22:27 Joseph Myers
2022-11-04 7:12 ` Florian Weimer [this message]
2022-11-04 9:28 ` Szabolcs Nagy
2022-11-04 16:48 ` H.J. Lu
2022-11-04 16:52 ` Florian Weimer
2022-11-04 17:28 ` Fangrui Song
2022-11-04 17:47 ` Florian Weimer
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=87a6572ny0.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).