https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77941
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
For what it is worth, on my machine, -m32 compiles fine. At runtime in gdb:
Program received signal SIGSEGV, Segmentation fault.
0x08048662 in f (__result=..., .__result=1,
n=<error reading variable: Cannot access memory at address 0x1>)
at pr77941.f90:8
Which is no surprise, we are trying to stuff a large integer into 32 bits and
it looks like its truncating and effectively wrapped around. So it gets down
to what kind of diagnostic do we want under -m32, if any?
