From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Configure GCC with --enable-initfini-array [BZ #27945]
Date: Wed, 9 Jun 2021 12:01:23 -0700 [thread overview]
Message-ID: <CAMe9rOokF-+rCbbt8jfYFe0FA9KmAK2PhX51_wdL_b+hLS27hw@mail.gmail.com> (raw)
In-Reply-To: <f6125c95-34fa-8dd6-3f7b-7365385fdb35@linaro.org>
On Wed, Jun 9, 2021 at 11:13 AM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
>
>
> On 09/06/2021 15:02, Joseph Myers wrote:
> > On Wed, 9 Jun 2021, H.J. Lu via Libc-alpha wrote:
> >
> >> I disagree. The behavior of the cross compiler should be as close to the native
> >> Linux system compiler, not other versions of cross compilers, as possible.
> >
> > But fixing that was the point of your GCC patch. I don't think working
> > around deficiencies in previous versions of GCC, that aren't necessary to
> > work around for building glibc, is within scope for build-many-glibcs.py;
> > it's enough that the bug (cross compiler different from native) was fixed
> > in the logically correct place (in GCC, for future GCC releases).
>
> But this also does not have any really drawback, correct?
>
> I thinking for the possible support to add a way to build a specific
> gcc/binutins/glibc version with build-many-glibcs.py.
See:
https://gitlab.com/hjl.tools/x86-64-linux-toolchain
--
H.J.
next prev parent reply other threads:[~2021-06-09 19:02 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 [this message]
2021-06-09 20:52 ` Joseph Myers
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=CAMe9rOokF-+rCbbt8jfYFe0FA9KmAK2PhX51_wdL_b+hLS27hw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--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).