Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>  -------Original Message-------
>  From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
>  To: Saifi Khan <saifi.khan@xxxxxxxxx>
>  Cc: gcc-help@xxxxxxxxxxx <gcc-help@xxxxxxxxxxx>
>  Subject: Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
>  Sent: 2024-01-18 13:00
>  
>  On Thu, 18 Jan 2024 at 12:39, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:
>  >
>  > On Thu, 18 Jan 2024 at 11:42, Saifi Khan <saifi.khan@xxxxxxxxx> 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?
>  
>  I've fixed the warnings at r14-8225-gac913d5d518604
>  

Sure thanks for your help.

git show ac913d5d518604c5baf7274bed76e3ff8f3e4c08 was of educational value.

warm regards
Saifi.



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux