From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS17314 8.43.84.0/22 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id C94A31F8C6 for ; Fri, 30 Jul 2021 20:52:37 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CE9EA39960FA for ; Fri, 30 Jul 2021 20:52:36 +0000 (GMT) Received: from esa1.mentor.iphmx.com (esa1.mentor.iphmx.com [68.232.129.153]) by sourceware.org (Postfix) with ESMTPS id D358139874CE for ; Fri, 30 Jul 2021 20:52:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D358139874CE Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mentor.com IronPort-SDR: wpinYraC18FfxZmueAOgNU3mrw3i/T/nAo+Ke0o7H/xJe0HPxvRHYEqiI9FZB8jmgawDbVffmm 5kGAdS/o36q+owStOM/EmEdNFa4uEn5fQag40rPZ4DgylpbIbA3q0tV5L7dRZ7qfcl4Rgin6r0 5vW0P2M3l+VxRKgb38ubmMhs8yCwZ5+uPCah2lax3HVsj7ftE0O55EDBAgoLL9k7iu0XxxEYFs 7l1147keDIn/O8G1c03vxuPV/h1LInGnXtbuoUdyomDFdWXWNciZVHsCRuOzNn/QvifBN8XW69 6gl9dpg6vvG4YRU37qf3eE+J X-IronPort-AV: E=Sophos;i="5.84,282,1620720000"; d="scan'208";a="66592309" Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa1.mentor.iphmx.com with ESMTP; 30 Jul 2021 12:52:24 -0800 IronPort-SDR: XvFagVXEMZN+DAGEyUyVqSHXN+YwShZMsPYKdssAh2c8WaJMOxG0aJtJPq5rsyde0EBtz4+Iy0 jCzCTpsAGaS4ZbsuXkf1cJs3qZOJRoISqLrOh9mUudhCJtx8n0EmI1kBpkKYI6G7bQxTIfyAfI DZ7i447FHXH2Z8sBFVM+W4e98hLOmMJCEY7fuflCFmTnkQNvb2y1UiXSGfKYfpJIO5PWt9wloj wsSa9kaLIRJRfdBilKhrtoaWgh1NpSn7WIYVNx8kPMjhM4M2KIwLGR09AF9fbEdVos7tVx3u7+ 1O0= Date: Fri, 30 Jul 2021 20:52:17 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Aldy Hernandez Subject: Re: Failures building glibc with mainline GCC In-Reply-To: Message-ID: References: User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) 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: , Cc: GCC Mailing List , Martin Sebor , libc-alpha@sourceware.org Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org Sender: "Libc-alpha" On Fri, 30 Jul 2021, Aldy Hernandez via Gcc wrote: > There's a new jump threader in GCC which is much more aggressive, and > may trigger latent problems with other warning passes, especially > -Warray-bounds, -Woverflow, and -Wuninitialized. > > Do your problems go away if you take out commit 2e96b5f14e? Reverting that commit fixes all the glibc build failures except for x86_64-linux-gnu, i686-gnu and powerpc64le-linux-gnu. -- Joseph S. Myers joseph@codesourcery.com