Re: LRA reload produces invalid insn

2018-11-01 Thread Vladimir Makarov
On 11/01/2018 08:25 PM, Paul Koning wrote: I'm running the testsuite on the pdp11 target, and I get a failure when using LRA that works correctly with the old allocator. The issue is that LRA is producing an insn that is invalid (it violates the constraints stated in the insn definition). Th

Re: LRA reload produces invalid insn

2018-11-01 Thread Peter Bergner
On 11/1/18 8:40 PM, Segher Boessenkool wrote: > Hi Peter, > > On Thu, Nov 01, 2018 at 07:49:36PM -0500, Peter Bergner wrote: >> On 11/1/18 7:25 PM, Paul Koning wrote: >>> I'm running the testsuite on the pdp11 target, and I get a failure when >>> using LRA that works correctly with the old alloca

Ping: Some MIPS patch need review and approval.

2018-11-01 Thread Paul Hua
Ping ? On Wed, Oct 31, 2018 at 8:30 PM Paul Hua wrote: > > Hi, GCC steering committee: > > There are some MIPS patches that need to be reviewed and approved. > > [PATCH v3 0/6] [MIPS] Reorganize the loongson march and extensions > instructions set. [1] > [PATCH v3 1/6] [MIPS] Split Loongson (MMI

Re: LRA reload produces invalid insn

2018-11-01 Thread Segher Boessenkool
Hi Peter, On Thu, Nov 01, 2018 at 07:49:36PM -0500, Peter Bergner wrote: > On 11/1/18 7:25 PM, Paul Koning wrote: > > I'm running the testsuite on the pdp11 target, and I get a failure when > > using LRA that works correctly with the old allocator. The issue is that > > LRA is producing an insn

Re: LRA reload produces invalid insn

2018-11-01 Thread Peter Bergner
On 11/1/18 7:25 PM, Paul Koning wrote: > I'm running the testsuite on the pdp11 target, and I get a failure when using > LRA that works correctly with the old allocator. The issue is that LRA is > producing an insn that is invalid (it violates the constraints stated in the > insn definition). [

LRA reload produces invalid insn

2018-11-01 Thread Paul Koning
I'm running the testsuite on the pdp11 target, and I get a failure when using LRA that works correctly with the old allocator. The issue is that LRA is producing an insn that is invalid (it violates the constraints stated in the insn definition). The insn in the IRA dump looks like this: (ins

gcc-7-20181101 is now available

2018-11-01 Thread gccadmin
Snapshot gcc-7-20181101 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20181101/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7

Patches for gcc/fortran and libgfortran need to be discussed and approved on fortran mailing list

2018-11-01 Thread Thomas Koenig
Hi, a gentle reminder: Patches which touch gcc/fortran or libgfortran need to be discussed on the fortran mailing list and approved by a reviewer. There have been a couple of commits recently where this wasn't followed, please remember to do so in the future. Regards Thomasa

Re: Suitable regression test for vectorizer patches? - (need {u,}madd* pattern)

2018-11-01 Thread Ramana Radhakrishnan
On Thu, Nov 1, 2018 at 10:42 AM Joern Wolfgang Rennecke wrote: > > > On 30/10/18 08:36, Richard Biener wrote: > > On Mon, Oct 29, 2018 at 7:03 PM Joern Wolfgang Rennecke > > wrote: > >> I want to submit some vectorizer patches, what would be a suitable > >> regression test? > > I am sure you have

Re: Suitable regression test for vectorizer patches? - (need {u,}madd* pattern)

2018-11-01 Thread Joern Wolfgang Rennecke
On 30/10/18 08:36, Richard Biener wrote: On Mon, Oct 29, 2018 at 7:03 PM Joern Wolfgang Rennecke wrote: I want to submit some vectorizer patches, what would be a suitable regression test? I am sure you have testcases, no? For new features please make them dg-do run ones by checking correctn