https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Weird memory corruption |[9/10/11/12 Regression]
|with multiple triggers |Weird memory corruption
| |with multiple triggers
--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Matt Thompson from comment #5)
Thanks for the additional checks.
> $ ./a.out
> opt_string.F90 122 T
> opt_string.F90 123 7
> err_msg: foo bar
>
> and NAG 7.0_7048 does:
>
> $ ./a.out
> opt_string.F90 122 T
> opt_string.F90 123 7
> err_msg: foo bar
Then, this is indeed a regression:
gcc-5.5:
/source/test/fortran/pr100651.F90 122 T
/source/test/fortran/pr100651.F90 123 32727
err_msg: foo bar
gcc-6-5;
/source/test/fortran/pr100651.F90 122 T
/source/test/fortran/pr100651.F90 123 32767
err_msg: foo bar ????H\?
gcc-7.5
/source/test/fortran/pr100651.F90 122 T
/source/test/fortran/pr100651.F90 123 32767
err_msg: foo bar0000????H\?
gcc8.5:
/source/test/fortran/pr100651.F90 122 T
/source/test/fortran/pr100651.F90 123 1569183428
t(23248,0x106ee05c0) malloc: can't allocate region
*** mach_vm_map(size=140734762573824) failed (error code=3)
t(23248,0x106ee05c0) malloc: *** set a breakpoint in malloc_error_break to
debug
Operating system error: Cannot allocate memory
Memory allocation failure in xrealloc
Error termination. Backtrace:
#0 0x106659f9d
.. etc.
