[Bug fortran/102460] fortran internal compile error in coverage.c

2021-11-04 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

Martin Liška  changed:

   What|Removed |Added

   Assignee|marxin at gcc dot gnu.org  |unassigned at gcc dot 
gnu.org

--- Comment #8 from Martin Liška  ---
Unassigning as it's a Fortran issue (where I asked at Fortran mailing list).

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-10-01 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

--- Comment #7 from Martin Liška  ---
Thanks! So it's really a Fortran issue

(gdb) p startloc.line
$8 = 7
(gdb) p end_line
$9 = 6

Can please anybody from Fortran FE guys help me here?

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-27 Thread davidsch at fedoraproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

--- Comment #6 from David Bold  ---
> What's meaning of the 'ENTRY ENTRY1()' directive?

It is an example, alternative entry point to the subroutine SUB1.

Here is some older documentation for the ENTRY directive:
https://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/Alternate-Entry-Points.html

Please excuse in case I got the question wrong ...

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-27 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

--- Comment #5 from Martin Liška  ---
> 
> I also do not see it on 11-branch, but that may be related to my local build.

Yes, I made a papering over it in the GCC-11 branch
(g:5f00ef3bc724e22628fdfd81855013115d115ebe).

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-27 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

Martin Liška  changed:

   What|Removed |Added

 CC||marxin at gcc dot gnu.org

--- Comment #4 from Martin Liška  ---
(In reply to David Bold from comment #1)
> I got around to compile the most recent version (git commit 2f2dcbe471) and
> with that I get:
> 
> MOD2.f:15:72:
> 
>15 |   END MODULE MOD2
>   | 
> ^
> Error: function starts on a higher line number than it ends
> [-Werror=coverage-invalid-line-number]
> f951: some warnings being treated as errors

It's very likely a front-end issue which is described in the warning message.
What's meaning of the 'ENTRY ENTRY1()' directive?

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-23 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

--- Comment #3 from anlauf at gcc dot gnu.org ---
Reduced testcase:

MODULE MOD2
  IMPLICIT NONE
CONTAINS
  SUBROUTINE SUB1()
  ENTRY ENTRY1()
  END SUBROUTINE SUB1
END MODULE MOD2

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-23 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

anlauf at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
  Known to fail||12.0
   Last reconfirmed||2021-09-23
 Ever confirmed|0   |1

--- Comment #2 from anlauf at gcc dot gnu.org ---
Confirmed.

The issue disappears if I comment out the line

  ENTRY ENTRY1()

I also do not see it on 11-branch, but that may be related to my local build.

[Bug fortran/102460] fortran internal compile error in coverage.c

2021-09-23 Thread davidsch at fedoraproject dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460

--- Comment #1 from David Bold  ---
I got around to compile the most recent version (git commit 2f2dcbe471) and
with that I get:

MOD2.f:15:72:

   15 |   END MODULE MOD2
  |   
^
Error: function starts on a higher line number than it ends
[-Werror=coverage-invalid-line-number]
f951: some warnings being treated as errors