public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Configure GCC with --enable-initfini-array [BZ #27945]
Date: Wed, 9 Jun 2021 10:46:21 -0700	[thread overview]
Message-ID: <CAMe9rOqjrcz4d_YQ3FSw2An6kcpHJkXJjoUqLYXHbWvU6HqU0g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2106091604180.360093@digraph.polyomino.org.uk>

On Wed, Jun 9, 2021 at 9:07 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Wed, 9 Jun 2021, H.J. Lu via Libc-alpha wrote:
>
> > Starting from GCC 12, the .init_array and .fini_array sections are enabled
> > unconditionally by
> >
> > commit 13a39886940331149173b25d6ebde0850668d8b9
> > Author: H.J. Lu <hjl.tools@gmail.com>
> > Date:   Tue Jun 8 16:09:24 2021 -0700
> >
> >     Always enable DT_INIT_ARRAY/DT_FINI_ARRAY on Linux
> >
> > configure GCC with --enable-initfini-array to enable them when using GCC
> > release branches.
> >
> > Fixes BZ #27945.
>
> The point of build-many-glibcs.py isn't to build a glibc that's in some
> sense optimal.  This option isn't needed to get glibc to build, and it
> doesn't add to the diversity of configurations covered by
> build-many-glibcs.py (actually, it reduces that diversity by making the
> configurations built with older GCC versions more similar to those built
> with GCC 12).  So I don't see adding this GCC configure option as within
> scope for build-many-glibcs.py.

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.   Can
you tell me which native Linux system compilers don't support
DT_INIT_ARRAY/DT_FINI_ARRAY?

-- 
H.J.

  reply	other threads:[~2021-06-09 17:46 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 [this message]
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
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=CAMe9rOqjrcz4d_YQ3FSw2An6kcpHJkXJjoUqLYXHbWvU6HqU0g@mail.gmail.com \
    --to=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).