Re: GCC Testsuite patches break AIX

2020-05-28 Thread Christophe Lyon via Gcc
On Wed, 27 May 2020 at 22:40, Alexandre Oliva wrote: > > On May 27, 2020, Christophe Lyon via Gcc wrote: > > > On Wed, 27 May 2020 at 16:26, Jeff Law via Gcc wrote: > > >> Any thoughts on the massive breakage on the embedded ports in the > >> testsuite? > > I wasn't aware of any. Indeed, one o

Re: GCC Testsuite patches break AIX

2020-05-27 Thread Alexandre Oliva
On May 27, 2020, Christophe Lyon via Gcc wrote: > On Wed, 27 May 2020 at 16:26, Jeff Law via Gcc wrote: >> Any thoughts on the massive breakage on the embedded ports in the testsuite? I wasn't aware of any. Indeed, one of my last steps before submitting the patchset was to fix problems that h

Re: GCC Testsuite patches break AIX

2020-05-27 Thread David Edelsohn via Gcc
On Wed, May 27, 2020 at 10:16 AM Alexandre Oliva wrote: > > Hello, David, > > On May 26, 2020, David Edelsohn wrote: > > > Complaints about -dA, -dD, -dumpbase, etc. > > This was the main symptom of the problem fixed in the follow-up commit > r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b > >

Re: GCC Testsuite patches break AIX

2020-05-27 Thread Christophe Lyon via Gcc
On Wed, 27 May 2020 at 16:26, Jeff Law via Gcc wrote: > > On Wed, 2020-05-27 at 11:16 -0300, Alexandre Oliva wrote: > > Hello, David, > > > > On May 26, 2020, David Edelsohn wrote: > > > > > Complaints about -dA, -dD, -dumpbase, etc. > > > > This was the main symptom of the problem fixed in the f

Re: GCC Testsuite patches break AIX

2020-05-27 Thread Jeff Law via Gcc
On Wed, 2020-05-27 at 11:16 -0300, Alexandre Oliva wrote: > Hello, David, > > On May 26, 2020, David Edelsohn wrote: > > > Complaints about -dA, -dD, -dumpbase, etc. > > This was the main symptom of the problem fixed in the follow-up commit > r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b >

Re: GCC Testsuite patches break AIX

2020-05-27 Thread Alexandre Oliva
Hello, David, On May 26, 2020, David Edelsohn wrote: > Complaints about -dA, -dD, -dumpbase, etc. This was the main symptom of the problem fixed in the follow-up commit r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b Could you please confirm that you did NOT have this commit in your failing