[Bug fortran/95631] Unable to redefine a literal with `-std=legacy'

2020-06-11 Thread ma...@linux-mips.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631

Maciej W. Rozycki  changed:

   What|Removed |Added

 Resolution|INVALID |DUPLICATE

--- Comment #5 from Maciej W. Rozycki  ---
Thanks for the clarification, and quoting the relevant pieces of the
respective standards in particular.

I have marked the relevant duplicates, and hopefully the somewhat more
meaningful bug summary will serve in the future.  It may be worth adding
this test case to the test suite, though for that I gather we'd have to
trap that SIGSEGV and convert it to a successful return, whereas running
through would have to exit unsuccessfully.  Regrettably my Fortran fu is
too weak to come up with a signal handler quickly.

NB numerous computer systems do not support memory protection and have
no way to mark a segment read-only, and may otherwise either not support
instrumentation at all or it can be disabled for performance reasons, so
the phenomenon observed/reported may indeed have been just a peculiarity
of the implementation.

I have filed PR target/95637 for the `.sdata' assignment of read-only
data with `riscv*-*-linux-gnu' targets.

*** This bug has been marked as a duplicate of bug 17887 ***

[Bug fortran/95631] Unable to redefine a literal with `-std=legacy'

2020-06-10 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631

kargl at gcc dot gnu.org changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||kargl at gcc dot gnu.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from kargl at gcc dot gnu.org ---
I think Eric Korpela may not know the Fortran standards.  Yes,
old compiler did dumb things, because it was/is difficult to
detect this violation of the Fortran standards.  Note, these
prohibitions are on the programmer.

F66 8.4.2

If an actual argument corresponds to a dummy argument that is
defined or redefined in the referenced subprogram, the actual
argument must be a variable name, an array element name, or an
array name.

F77 15.9.2

Actual arguments may be constants, symbolic names of constants,
function references, expressions involving operators, and
expressions enclosed in parentheses if and only if the associated
dummy argument is a variable that is not defined during execution
of the referenced external procedure.

[Bug fortran/95631] Unable to redefine a literal with `-std=legacy'

2020-06-10 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631

--- Comment #3 from Andrew Pinski  ---
Note I think this is a bug in the RISCV backend that selects the small data
section for read only constants.  Rather than we want to support this
extension.

[Bug fortran/95631] Unable to redefine a literal with `-std=legacy'

2020-06-10 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631

--- Comment #2 from Andrew Pinski  ---
PR 17887 was the same issue against g77.

[Bug fortran/95631] Unable to redefine a literal with `-std=legacy'

2020-06-10 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631

--- Comment #1 from Andrew Pinski  ---
Well we decided long time ago not to support that extension.
See PR 37974 and maybe even some g77 bug reports.