Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Andreas Schwab
This breaks bootstrap with go. ../../gcc/go/gofrontend/go-diagnostics.cc: In function 'std::string expand_message(const char*, va_list)': ../../gcc/go/gofrontend/go-diagnostics.cc:110:61: error: '' may be used uninitialized [-Werror=maybe-uninitialized] 110 | "memory alloc

Re: Re: typeof and operands in named address spaces

2020-11-15 Thread Uecker, Martin
> On Wed, Nov 04, 2020 at 07:31:42PM +0100, Uros Bizjak wrote: > > Hello! > >  > > I was looking at the recent linux patch series [1] where segment > > qualifiers (named address spaces) were introduced to handle percpu > > variables. In the patch [2], the author mentions that: > >  > > --q-- > > U

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Jan Hubicka
> This breaks bootstrap with go. > > ../../gcc/go/gofrontend/go-diagnostics.cc: In function 'std::string > expand_message(const char*, va_list)': > ../../gcc/go/gofrontend/go-diagnostics.cc:110:61: error: '' may be > used uninitialized [-Werror=maybe-uninitialized] > 110 |

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Rainer Orth
Hi Jan, >> This breaks bootstrap with go. >> >> ../../gcc/go/gofrontend/go-diagnostics.cc: In function 'std::string >> expand_message(const char*, va_list)': >> ../../gcc/go/gofrontend/go-diagnostics.cc:110:61: error: '' may >> be used uninitialized [-Werror=maybe-uninitialized] >> 110 |

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Jan Hubicka
> Hi Jan, > > >> This breaks bootstrap with go. > >> > >> ../../gcc/go/gofrontend/go-diagnostics.cc: In function 'std::string > >> expand_message(const char*, va_list)': > >> ../../gcc/go/gofrontend/go-diagnostics.cc:110:61: error: '' may > >> be used uninitialized [-Werror=maybe-uninitialized]

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Rainer Orth
Hi Jan, >> I'm seeing the same on both i386-pc-solaris2.11 and >> sparc-sun-solaris2.11, so I don't think there are special configure >> flags involved. > > When I configure with ../configure --enable-languages=go my build > eventually finishes fine on curren trunk: [...] > On Debian SLES machines

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Jan Hubicka
> Hi Jan, > > >> I'm seeing the same on both i386-pc-solaris2.11 and > >> sparc-sun-solaris2.11, so I don't think there are special configure > >> flags involved. > > > > When I configure with ../configure --enable-languages=go my build > > eventually finishes fine on curren trunk: > [...] > > On

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread H.J. Lu via Gcc
On Fri, Nov 13, 2020 at 12:07 AM Richard Biener wrote: > > On Tue, 10 Nov 2020, Jan Hubicka wrote: > > > Hi, > > here is updaed patch. > > > > Honza > > > > Bootstrapped/regtested x86_64-linux, OK (after the fnspec fixes)? > > OK. > > Thanks, > Richard. > This caused: https://gcc.gnu.org/bugzill

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Jan Hubicka
> On Fri, Nov 13, 2020 at 12:07 AM Richard Biener wrote: > > > > On Tue, 10 Nov 2020, Jan Hubicka wrote: > > > > > Hi, > > > here is updaed patch. > > > > > > Honza > > > > > > Bootstrapped/regtested x86_64-linux, OK (after the fnspec fixes)? > > > > OK. > > > > Thanks, > > Richard. > > > > This

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Rainer Orth
Hi Jan, >> > When I configure with ../configure --enable-languages=go my build >> > eventually finishes fine on curren trunk: >> [...] >> > On Debian SLES machines. Having preprocessed go-diagnostics.cc and >> > .uninit1 dump would probably help. >> >> apart from go/diagnostics.cc, I see the war

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Andreas Schwab
See PR97840. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Jan Hubicka
> See PR97840. Thanks, this is a false positive where we fail to discover that pointed-to type is empty on non-x86_64 targets. This is triggered by better alias analysis caused by non-escape discovery. While this is not a full fix (I hope someone with more experience on C++ types and warnings wil

gcc-11-20201115 is now available

2020-11-15 Thread GCC Administrator via Gcc
Snapshot gcc-11-20201115 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20201115/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

`PatchSet' API mismatch causing a total `contrib/mklog.py' failure?

2020-11-15 Thread Maciej W. Rozycki
Hi Martin, I have decided to give your `contrib/mklog.py' script a hit and, well, ahem, I guess I must be doing something utterly silly, but no matter what kind of a diff I hand to the script it does not produce anything unless I apply a patch like below to it, in which case the output produce

Re: `PatchSet' API mismatch causing a total `contrib/mklog.py' failure?

2020-11-15 Thread Martin Liška
On 11/16/20 12:17 AM, Maciej W. Rozycki wrote: Hi Martin, Hello. I have decided to give your `contrib/mklog.py' script a hit and, well, ahem, I guess I must be doing something utterly silly, but no matter what kind of a diff I hand to the script it does not produce anything unless I apply

Re: Detect EAF flags in ipa-modref

2020-11-15 Thread Richard Biener
On Sun, 15 Nov 2020, Jan Hubicka wrote: > > See PR97840. > Thanks, > this is a false positive where we fail to discover that pointed-to type > is empty on non-x86_64 targets. This is triggered by better alias > analysis caused by non-escape discovery. > > While this is not a full fix (I hope som