From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Add tests with a local IFUNC resolver [BZ #23937]
Date: Mon, 11 Mar 2019 12:16:52 +0100 (CET) [thread overview]
Message-ID: <765038260.19567.1552303012823@poczta.nazwa.pl> (raw)
In-Reply-To: <56767244.124440.1551692830069@poczta.nazwa.pl>
4.03.2019 10:47 Rafal Luzynski <digitalfreak@lingonborough.com> wrote:
>
> 2.03.2019 17:54 "H.J. Lu" <hjl.tools@gmail.com> wrote:
> >
> > [...]
> > GCC 6.4.1 and binutils 2.31 branch work for me on x86-64.
>
> Still the same failure.
>
> I've also checked a similar virtual machine on another physical
> machine and again the same failure which confirms that it is not
> anything specific to one CPU model.
>
> Does it maybe matter that all my tests are performed in virtual
> machines controlled by VirtualBox?
I've made several more tests during the weekend and it seems that
it's GCC version what matters. Just to summarize: my basic test
environment is Fedora 24 (yes, I know, it is old) but I am able to
install packages from newer versions. I definitely have not tested
every single version of GCC but 7.2.1-2 and everything newer worked
fine while 7.1.1-3 and everything older failed at these tests.
I did not touch binutils during these tests so I assume that its
version does not matter.
Thoughts? Should we state that GCC 7.2 is a minimum required version
to build Glibc? Should these tests have additional checks and XFAIL
in some versions of GCC? Should we assume that the failures are
correct and Glibc may be compiled with that particular version of GCC
but only if GCC has some patches fixing any known bugs?
Also, it's likely that it's not GCC what is problematic but some
other package pulled by GCC, for example libtool.
Please help.
Regards,
Rafal
next prev parent reply other threads:[~2019-03-11 11:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 12:53 [PATCH] elf: Add tests with a local IFUNC resolver [BZ #23937] Florian Weimer
2019-02-20 13:16 ` H.J. Lu
2019-02-20 13:29 ` Florian Weimer
2019-02-20 14:01 ` Szabolcs Nagy
2019-02-27 10:27 ` Florian Weimer
2019-03-01 0:50 ` Rafal Luzynski
2019-03-01 1:52 ` H.J. Lu
2019-03-01 8:25 ` Rafal Luzynski
2019-03-01 8:41 ` Florian Weimer
2019-03-01 11:03 ` Rafal Luzynski
2019-03-01 12:37 ` H.J. Lu
2019-03-02 0:34 ` Rafal Luzynski
2019-03-02 16:54 ` H.J. Lu
2019-03-04 9:47 ` Rafal Luzynski
2019-03-11 11:16 ` Rafal Luzynski [this message]
2019-03-11 13:55 ` Florian Weimer
2019-03-11 21:56 ` Rafal Luzynski
2019-03-12 1:12 ` H.J. Lu
2019-03-13 21:10 ` Florian Weimer
2019-03-13 11:47 ` Rafal Luzynski
2019-03-13 21:15 ` Florian Weimer
2019-02-27 21:23 ` H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=765038260.19567.1552303012823@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.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).