From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from s411.sureserver.com (s411.sureserver.com [192.252.151.33]) by sourceware.org (Postfix) with ESMTPS id B9860385782F for ; Thu, 18 Jan 2024 13:54:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B9860385782F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=nishan.io Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=nishan.io ARC-Filter: OpenARC Filter v1.0.0 sourceware.org B9860385782F Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=192.252.151.33 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705586064; cv=none; b=Oyrc4BJwjGdwFrWq/BeTF7BW/IH6jJ3MaglbA9UQcCpQ2qf0jg72Y+IFh897jzyvjewdKoIy2pDJxjNOLULoLCrJbhvO87NES5hJJzarZ91XNiOk1sMuz2Wwpb47WUqkSWJnUnDVpefAui/DGJYwUmCdrwyvV17bW7mXbICqJ1g= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705586064; c=relaxed/simple; bh=ohwtfcbPI7D4LIk1WXKvtdh576AnN2lUd7D22VXp1go=; h=DKIM-Signature:Message-ID:From:To:Subject:Date:MIME-Version; b=hg+LbY813R/SXOnWjvZ+2F32OFtlk6A4u+UpUy+EAHruq6+uZFOL5Lr/JVNXik9AhAgZlYUIAZymGGaXsd2IcKaByVibnt+kpjfs7p3a4g0/ksiY/vc4uCjYjzBQnohHimtSeeQD52oxoqeq4Fn34zf0sO99rykhEAZGA5ls78U= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=nishan.io; h=message-id :reply-to:from:to:subject:date:mime-version:in-reply-to :references:content-type:content-transfer-encoding; s=dkim; bh=o hwtfcbPI7D4LIk1WXKvtdh576AnN2lUd7D22VXp1go=; b=SdPN7J/NBiBZhK9C8 NUuujoMAdjzOXL/LG6261OjkOWfc/Zw3+Mj0s8IOqIlf3uec0bYi1r+ERP8m1Kwr ip5DIA7+xPZpRKxko+vLsWIVx4T75f+qoirS9aoAEx9aIi7dcgjyeiyXUeeDPrJM //n/VnkkHPFfCEOZ9W2n+0FIW4= Received: (qmail 64837 invoked by uid 1900); 18 Jan 2024 13:54:22 -0000 Message-ID: <20240118135422.64836.qmail@s411.sureserver.com> Reply-To: "=?utf-8?Q?Saifi=20Khan?=" From: "=?utf-8?Q?Saifi=20Khan?=" To: gcc-help@gcc.gnu.org Subject: =?utf-8?B?UmU6IGxpYnN0ZGMrKyBidWlsZCBlcnJvcjog4oCYX192YWxfYeKAmSBtYXkgYmUgdXNlZCB1bmluaXRpYWxpemVkIFstV2Vycm9yPW1heWJlLXVuaW5pdGlhbGl6ZWRd?= Date: Thu, 18 Jan 2024 13:54:21 +0000 MIME-Version: 1.0 X-Mailer: WebMail 2.55.13.14 X-Suremail-Sender: 103_199_139_51 X-Originating-Email: saifi.khan@nishan.io In-Reply-To: References: <20240118114134.56244.qmail@s411.sureserver.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > -------Original Message------- > From: Jonathan Wakely via Gcc-help > To: Saifi Khan > Cc: gcc-help@gcc.gnu.org > Subject: Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized] > Sent: 2024-01-18 12:41 > > On Thu, 18 Jan 2024 at 11:42, Saifi Khan wrote: > > > > Hi: > > > > Building gcc from the 'main' branch (4a8430c8c) and get this error during the 'libstdc++' automated build. > > > > Short of using '-Wno-error=maybe-uninitialized' is there any other approach that can be adopted ? > > What options are you using that turn on -Werror in the first place? > The entire build is driven using '/opt/gcc/src/configure' script. There are no flags that explicitly set '-Werror'. In case the build compiler version matters, i am using gcc version 13.2.1 20230801 (GCC) on ArchLinux/AMD64. warm regards Saifi.