From: "Saifi Khan" <saifi.khan@nishan.io>
To: gcc-help@gcc.gnu.org
Subject: Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
Date: Thu, 18 Jan 2024 13:54:21 +0000 [thread overview]
Message-ID: <20240118135422.64836.qmail@s411.sureserver.com> (raw)
In-Reply-To: <CAH6eHdRE5sEbQjY4aR2NEXz2zMBOP_J-ickwq8T78QzmB4fzHA@mail.gmail.com>
> -------Original Message-------
> From: Jonathan Wakely via Gcc-help <gcc-help@gcc.gnu.org>
> To: Saifi Khan <saifi.khan@nishan.io>
> Cc: gcc-help@gcc.gnu.org <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 <saifi.khan@nishan.io> 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.
prev parent reply other threads:[~2024-01-18 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:41 Saifi Khan
2024-01-18 12:39 ` Jonathan Wakely
2024-01-18 12:55 ` Jonathan Wakely
2024-01-18 14:09 ` Saifi Khan
2024-01-18 13:54 ` Saifi Khan [this message]
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=20240118135422.64836.qmail@s411.sureserver.com \
--to=saifi.khan@nishan.io \
--cc=gcc-help@gcc.gnu.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).