https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100
--- Comment #5 from Angus Gibson ---
I agree that it's not ideal... Unfortunately an awkward file format, and
fortran is usually the wrong language for this kind of IO anyway. I guess the
note that "A processor may prohibit some control character
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100
--- Comment #2 from Angus Gibson ---
Created attachment 47037
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47037&action=edit
Reproducing example (gz)
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: angus at agibson dot me
Target Milestone: ---
Created attachment 47036
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47036&action=edit
Reproducing example
I have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786
--- Comment #11 from Angus Gibson ---
Apologies if this is unrelated to the issue at hand (I don't quite understand
how everything is inter-related yet), but maybe it helps. First up, here's what
valgrind says about the segfault:
...
loc(cs%v(2)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786
--- Comment #2 from Angus Gibson ---
Changing the declaration of e to also be 'target', and associating the pointer:
CS%v(2)%p => e
if (query_ptr(e, CS)) then
...
still causes the segfault. Perhaps I disconnected this from the orig
Assignee: unassigned at gcc dot gnu.org
Reporter: angus at agibson dot me
Target Milestone: ---
Created attachment 44132
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44132&action=edit
Segfaulting example
I've run into a bit of a heisenbug regarding the associat