From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) by sourceware.org (Postfix) with ESMTPS id AA0C53857C4F for ; Wed, 9 Jun 2021 18:13:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AA0C53857C4F Received: by mail-qv1-xf2b.google.com with SMTP id g12so13281697qvx.12 for ; Wed, 09 Jun 2021 11:13:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BGnrYwRauOAKL6zp4TneMlHBaAiOwcnFCl3hGKxQmzw=; b=kJyyui4ctkhAbCWUT9RHoRyYPYmK1qdaI4t68pTQRqXoVlRp80ZdLBBPcd8fujy4kk qn6empjg6PPTNQSBECveLTlXAeX159kPkxoNVFP8GLAYoddRxvx9KkxGEae90h5tA/Zr /8u5NfKF1b5pE7CPlQbbp+SCaKwuOPm32qCS+UK0KncvHPOS/kp+vD1V7gQ3FgV8kDq3 P8nO14fHLyY8SZVUxn94+wFdbTm7CR7MkZt3g1Twiw51kHqUgipXONAmzouiY8PqrdkA H32w1YmZnO5PYDeQgjXycbWsSGwjjg4+aNxOVDl1ObMfAfIKkO5SKeG1wOvecHEdTyIz iUWw== X-Gm-Message-State: AOAM532cBcFRyS8at1c7SWlEWqVfQQGT7ClaVFa1ZLX70pjWqswJiNyS LCtnys+VhsKJZ+te10VaZ+NvwLDGLDe6qQ== X-Google-Smtp-Source: ABdhPJwVJDJaiVyeDwIuR4IA8nwkYlBXH2RfvLI9odTfyNYwsP89DBxKABGoCigEh/IvedS0W8rQcQ== X-Received: by 2002:ad4:596c:: with SMTP id eq12mr1311428qvb.30.1623262393972; Wed, 09 Jun 2021 11:13:13 -0700 (PDT) Received: from [192.168.1.4] ([177.194.59.218]) by smtp.gmail.com with ESMTPSA id p12sm496759qtw.61.2021.06.09.11.13.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Jun 2021 11:13:13 -0700 (PDT) Subject: Re: [PATCH] Configure GCC with --enable-initfini-array [BZ #27945] To: libc-alpha@sourceware.org References: <20210609122916.3884385-1-hjl.tools@gmail.com> From: Adhemerval Zanella Message-ID: Date: Wed, 9 Jun 2021 15:13:11 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, 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 18:13:15 -0000 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.