From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id E7F85399BC15 for ; Wed, 9 Jun 2021 17:46:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E7F85399BC15 Received: by mail-pf1-x42a.google.com with SMTP id q25so18994414pfh.7 for ; Wed, 09 Jun 2021 10:46:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=miB8l7D2JRFEe+FcIMb/GLC8T/92DZSBCrndSha1rvU=; b=fqfYT2uBGNHOg+3i//RZzcsNXQ9OeJVdUV+AoSvg/IHDClKIWh+nVNNxvpsZ00sNAq 4kp0va7fG16YfEEOypaQ15hSBtN//tbE26W3crDAcFs5mUlkeqeEf7g1z1vilXAm04MS RGHhwFeOLgfR5ltfmSGoKl8D4byj4plNn06S+fRWZr+WMolA73gduFF3wjyL19xztnC5 rr49qxsj536/QVb4zy8ctoGjWoIgwL5+G31viOwB/hx9qrV5czT1YE0nfMofd08FREh7 1LIDmuy/h/+mHV3leZuk4fPkS2HpZSoOztKzI+i3+azcx7LjYc+Ghclb8BYZ8ow/IRve oEUg== X-Gm-Message-State: AOAM532U+VsivXmQym9U0WtPMU362HChHoPG5NXKmYVjD0NktG+M1Ea9 PTsnpqP4nn/IOelHAKM5mVitsf0XT0e8aSAfrxHI/y/eg7k= X-Google-Smtp-Source: ABdhPJzyM/rIQqUk8Aa7KsCUw4wHKreZka9rShetRuionPx87SzSO1aotrW3vGO4d2Uzv4f+Lz6J6uSLKXeb+FvyyYk= X-Received: by 2002:aa7:9983:0:b029:2e9:e086:7917 with SMTP id k3-20020aa799830000b02902e9e0867917mr807885pfh.57.1623260817040; Wed, 09 Jun 2021 10:46:57 -0700 (PDT) MIME-Version: 1.0 References: <20210609122916.3884385-1-hjl.tools@gmail.com> In-Reply-To: From: "H.J. Lu" Date: Wed, 9 Jun 2021 10:46:21 -0700 Message-ID: Subject: Re: [PATCH] Configure GCC with --enable-initfini-array [BZ #27945] To: Joseph Myers Cc: GNU C Library Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3026.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2021 17:47:03 -0000 On Wed, Jun 9, 2021 at 9:07 AM Joseph Myers 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 > > 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.