Re: [Patch, Fortran] PR 50163 - ICE with nonconst expr in init expr

2011-08-25 Thread Mikael Morin
On Wednesday 24 August 2011 15:31:17 Tobias Burnus wrote: > > Isn't there some rules about backporting? The way we do it now, it > > looks completely arbitrary. > > I think it *is* arbitrary - and unavoidable so. > > The main idea behind regression fixing is to make sure that what once > worked s

Re: [Patch, Fortran] PR 50163 - ICE with nonconst expr in init expr

2011-08-24 Thread Tobias Burnus
On 08/24/2011 12:12 PM, Mikael Morin wrote: On Tuesday 23 August 2011 14:26:59 Tobias Burnus wrote: OK for the trunk? OK. Thanks for the review! Committed to the 4.7 trunk (Rev. 178038); I will backport the patch later. (For cross-readers: That's a patch for a 4.3+ ice-on-invalid-code regre

Re: [Patch, Fortran] PR 50163 - ICE with nonconst expr in init expr

2011-08-24 Thread Mikael Morin
On Tuesday 23 August 2011 14:26:59 Tobias Burnus wrote: > The bug is a regression: An error was printed with 4.1.x but since 4.3.x > one gets an ICE. [No idea what GCC 4.2 does.] The solution is simply: > Returning if there is a MATCH_ERROR. > > See PR (esp. comment 2) for a more detailed descript

[Patch, Fortran] PR 50163 - ICE with nonconst expr in init expr

2011-08-23 Thread Tobias Burnus
The bug is a regression: An error was printed with 4.1.x but since 4.3.x one gets an ICE. [No idea what GCC 4.2 does.] The solution is simply: Returning if there is a MATCH_ERROR. See PR (esp. comment 2) for a more detailed description: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50163#c0 Buil