https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95631
Maciej W. Rozycki <ma...@linux-mips.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |DUPLICATE
--- Comment #5 from Maciej W. Rozycki <ma...@linux-mips.org> ---
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 ***
