public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Add a comment for --enable-initfini-array [BZ #27945]
Date: Sat, 13 Nov 2021 17:50:28 +0000 (GMT)	[thread overview]
Message-ID: <20211113175028.641093858410@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=cbcd65c8b526555d9b98628338973f91f74002ad

commit cbcd65c8b526555d9b98628338973f91f74002ad
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Nov 8 07:49:11 2021 -0800

    Add a comment for --enable-initfini-array [BZ #27945]
    
    Document that --enable-initfini-array is enabled by default in GCC 12,
    which can be removed when GCC 12 becomes the minimum requirement.

Diff:
---
 scripts/build-many-glibcs.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index e8b9b213ca..6ae2172956 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -1445,7 +1445,9 @@ class Config(object):
         # checking support.  libcilkrts does not support GNU/Hurd (and
         # has been removed in GCC 8, so --disable-libcilkrts can be
         # removed once glibc no longer supports building with older
-        # GCC versions).
+        # GCC versions).  --enable-initfini-array is enabled by default
+        # in GCC 12, which can be removed when GCC 12 becomes the
+        # minimum requirement.
         cfg_opts = list(self.gcc_cfg)
         cfg_opts += ['--enable-initfini-array']
         cfg_opts += ['--disable-libssp', '--disable-libcilkrts']


                 reply	other threads:[~2021-11-13 17:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211113175028.641093858410@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=glibc-cvs@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).