From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Configure GCC with --enable-initfini-array [BZ #27945]
Date: Wed, 9 Jun 2021 20:52:55 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2106092047180.360093@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOokF-+rCbbt8jfYFe0FA9KmAK2PhX51_wdL_b+hLS27hw@mail.gmail.com>
On Wed, 9 Jun 2021, H.J. Lu via Libc-alpha wrote:
> See:
>
> https://gitlab.com/hjl.tools/x86-64-linux-toolchain
That looks like it has different scope and goals from
build-many-glibcs.py.
As another example, build-many-glibcs.py doesn't build GCC with ISL -
because that's not relevant to testing different glibc configurations, so
adding ISL to the build would just add extra irrelevant complications.
As another example closer to the present case, you're using
--enable-gnu-indirect-function. That option can definitely be relevant to
the glibc build - but we also want glibc to be able to build with GCC
versions not defaulting to enabling that option on all relevant
architectures, and adding that option in build-many-glibcs.py on relevant
architectures would both reduce test coverage and lead to extra duplicated
knowledge in build-many-glibcs.py about which architectures that option is
relevant on.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-06-09 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:29 H.J. Lu
2021-06-09 16:07 ` Joseph Myers
2021-06-09 17:46 ` H.J. Lu
2021-06-09 18:02 ` Joseph Myers
2021-06-09 18:13 ` Adhemerval Zanella
2021-06-09 19:01 ` H.J. Lu
2021-06-09 20:52 ` Joseph Myers [this message]
2021-06-09 20:44 ` Joseph Myers
2021-11-05 19:45 ` Adhemerval Zanella
2021-11-05 22:09 ` H.J. Lu
2021-11-08 15:01 ` Joseph Myers
2021-11-08 15:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2106092047180.360093@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--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).