From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id BD2273851416; Thu, 29 Jul 2021 18:34:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD2273851416
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100651] [9/10/11/12 Regression] Weird memory corruption
 with multiple triggers
Date: Thu, 29 Jul 2021 18:34:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 11.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-100651-4-bZFuEDCygf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-100651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-100651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 18:34:14 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100651

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
>=20
> and NAG 7.0_7048 does:
>=20
> $ ./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=3D140734762573824) failed (error code=3D3)
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.=