Re: [Fortran, Patch] Fix #line parsing

2012-07-18 Thread Tobias Burnus
On 07/17/2012 11:29 PM, Tobias Burnus wrote: Mikael Morin wrote: On 17/07/2012 20:52, Tobias Burnus wrote: Build and regtested on x86-64-gnu-linux. OK for the trunk? I should have bootstrapped and not just build the patch. It then fails in libgfortran: Warning: libgfortran/kinds-override.h

Re: [Fortran, Patch] Fix #line parsing

2012-07-17 Thread Tobias Burnus
Mikael Morin wrote: On 17/07/2012 20:52, Tobias Burnus wrote: Build and regtested on x86-64-gnu-linux. OK for the trunk? Sorry, I hit "Sent" a tad too early. The patch failed because it was also parsing the first few lines of a cpped file, which are, e.g., # 1 "gfortran.dg/g77/cpp4.F" # 1 "

Re: [Fortran, Patch] Fix #line parsing

2012-07-17 Thread Mikael Morin
On 17/07/2012 20:52, Tobias Burnus wrote: > gfortran properly handles the "#line" which come from #include > statements and look as > > # 1234 "include_file_name.f90" 1 > > Here, the syntax is "# linenumber filename flags", where flags is a > space-delimited list of the flags 1,2,3, or 4. The pro

[Fortran, Patch] Fix #line parsing

2012-07-17 Thread Tobias Burnus
gfortran properly handles the "#line" which come from #include statements and look as # 1234 "include_file_name.f90" 1 Here, the syntax is "# linenumber filename flags", where flags is a space-delimited list of the flags 1,2,3, or 4. The problem is that the gfortran didn't handle the case of