public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: Mon, 8 Nov 2021 15:01:02 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2111081459340.2331687@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOrJdNmduoBZSu+ba39NJ+eevxvdFbzd_Bh2T=V+GWN+9A@mail.gmail.com>

On Fri, 5 Nov 2021, H.J. Lu wrote:

> I am checking in this patch now.

Please see my previous comment.  If adding such a configure option that 
won't be needed with future GCC versions, you also need to add a comment 
saying what GCC version makes that option no longer required.

> > > It's one more thing to track when to remove when the minimum GCC version
> > > for building glibc increases.  (We have such a comment on the use of
> > > --disable-libcilkrts.  We ought to have one on the use of
> > > --disable-libmpx.  If we used --enable-initfini-array, that should have
> > > such a comment as well.)

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2021-11-08 15:01 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
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 [this message]
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.2111081459340.2331687@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).