Question about source file location when one uses #line 1 "example2.in" directive

Question about source file location when one uses #line 1 "example2.in" directive

[Martin Liška]

Hello.

I've been working on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78792, where one provides
#line directive. Problem is that in ipa-profile.c I see:

$ cat ~/Programming/testcases/pr78792.f90
#line 10 "example.in"
PROGRAM example
PRINT *, "example"
END PROGRAM

$ (gdb) p curr_location
$1 = {file = 0x21e2c70 "/home/marxin/Programming/testcases/pr78792.f90", line = 12, column = 0, data = 0x0, sysp = false}

line is fine, however file isn't. The very same source code works fine for *.i files, where file is changed properly.
Can you please help me where to investigate?

Thanks,
Martin

Re: Question about source file location when one uses #line 1 "example2.in" directive

[Martin Liška]

Gentle PING^1

> Hello.
>
> I've been working on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78792, where one provides
> #line directive. Problem is that in ipa-profile.c I see:
>
> $ cat ~/Programming/testcases/pr78792.f90
> #line 10 "example.in"
> PROGRAM example
> PRINT *, "example"
> END PROGRAM
>
> $ (gdb) p curr_location
> $1 = {file = 0x21e2c70 "/home/marxin/Programming/testcases/pr78792.f90", line = 12, column = 0, data = 0x0, sysp = false}
>
> line is fine, however file isn't. The very same source code works fine for *.i files, where file is changed properly.
> Can you please help me where to investigate?
>
> Thanks,
> Martin
>

Re: Question about source file location when one uses #line 1 "example2.in" directive

[Thomas Koenig]

Hello Martin,

>> I've been working on
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78792, where one provides
>> #line directive. Problem is that in ipa-profile.c I see:
>>
>> $ cat ~/Programming/testcases/pr78792.f90
>> #line 10 "example.in"
>> PROGRAM example
>> PRINT *, "example"
>> END PROGRAM

The place to start work on this would probably in scanner.c,
gfc_define_undef_line, which handles lines starting out with #.
I don't see anything there handling #line directives, so this looks
like an obvious place to start.

HTH

	Thomas

Re: Question about source file location when one uses #line 1 "example2.in" directive

[Martin Liška]

On 04/19/2017 10:31 AM, Thomas Koenig wrote:
> Hello Martin,
>
>>> I've been working on
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78792, where one provides
>>> #line directive. Problem is that in ipa-profile.c I see:
>>>
>>> $ cat ~/Programming/testcases/pr78792.f90
>>> #line 10 "example.in"
>>> PROGRAM example
>>> PRINT *, "example"
>>> END PROGRAM
>
> The place to start work on this would probably in scanner.c,
> gfc_define_undef_line, which handles lines starting out with #.
> I don't see anything there handling #line directives, so this looks
> like an obvious place to start.
>
> HTH
>
>     Thomas
>

The place only handles #define and #undefine. Looks there's no place where '#line'
prefix is parsed. To be honest, I'm not able to compile a pre-processed Fortran file:

$ gfortran example2.f90 --coverage -cpp  -E > example.f
$ cat example.f
# 1 "example2.f90"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "example2.f90"

# 1 "example2.in" 1

# 1 "inc" 1
# 2 "example2.in" 2




PROGRAM example2
PRINT *, "example2"
END PROGRAM
# 2 "example2.f90" 2


$ gfortran example.f --coverage
example2.in:6:1:

  PROGRAM example2
  1
Error: Non-numeric character in statement label at (1)
example2.in:6:1:
..


Same with adding '-fpreprocessed' option when added.

Thanks,
Martin

Re: Question about source file location when one uses #line 1 "example2.in" directive

[Steve Kargl]

On Wed, Apr 19, 2017 at 04:18:28PM +0200, Martin Liška wrote:
> prefix is parsed. To be honest, I'm not able to compile a pre-processed Fortran file:
> 
> $ gfortran example2.f90 --coverage -cpp  -E > example.f

> 
> $ gfortran example.f --coverage
> example2.in:6:1:
> 
>   PROGRAM example2
>   1
> Error: Non-numeric character in statement label at (1)
> example2.in:6:1:

You need to understand the filename suffix convention.
A filename ending in .f is assumed to be in fixed-form
format.  A filename ending in .f90 is in free-form
format.  See the gfortran for a complete description
of the filename convention.  If the output of your
first command line does not conform to the fixed-form
format for .f (or free-form format for .f90), then 
gfortran will chock with your second command line.

-- 
Steve
20161221 https://www.youtube.com/watch?v=IbCHE-hONow

Re: Question about source file location when one uses #line 1 "example2.in" directive

[Martin Liška]

On 04/19/2017 05:06 PM, Steve Kargl wrote:
> On Wed, Apr 19, 2017 at 04:18:28PM +0200, Martin Liška wrote:
>> prefix is parsed. To be honest, I'm not able to compile a pre-processed Fortran file:
>>
>> $ gfortran example2.f90 --coverage -cpp  -E > example.f
> 
>>
>> $ gfortran example.f --coverage
>> example2.in:6:1:
>>
>>   PROGRAM example2
>>   1
>> Error: Non-numeric character in statement label at (1)
>> example2.in:6:1:
> 
> You need to understand the filename suffix convention.
> A filename ending in .f is assumed to be in fixed-form
> format.  A filename ending in .f90 is in free-form
> format.  See the gfortran for a complete description
> of the filename convention.  If the output of your
> first command line does not conform to the fixed-form
> format for .f (or free-form format for .f90), then 
> gfortran will chock with your second command line.
> 

Thanks for clarification, works for me :)
(as one can see here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78792#c3)

Martin