From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E495C385480A; Tue, 13 Apr 2021 22:09:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E495C385480A From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/100071] New: Test case libgomp.fortran/alloc-2.F90 fails with invalid memory reference Date: Tue, 13 Apr 2021 22:09:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2021 22:09:42 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100071 Bug ID: 100071 Summary: Test case libgomp.fortran/alloc-2.F90 fails with invalid memory reference Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:fff15bad1ab571906c37b88380431768d917dcb0, r11-2101 The commit above is where this test case was introduced and it fails both t= here and with current trunk. The following runs were on a power 8 BE machine. I did not see failures on LE. This is kind of odd. If I run the test case like this the 64 bit run fails: make -k check-target-libgomp RUNTESTFLAGS=3D"--target_board=3Dunix'{-m32,-= m64}' fortran.exp=3Dlibgomp.fortran/alloc-2.F90" =3D=3D=3D libgomp tests =3D=3D=3D Running target unix/-m32 =3D=3D=3D libgomp Summary for unix/-m32 =3D=3D=3D # of expected passes 2 Running target unix/-m64 FAIL: libgomp.fortran/alloc-2.F90 -O execution test =3D=3D=3D libgomp Summary for unix/-m64 =3D=3D=3D # of expected passes 1 # of unexpected failures 1 =3D=3D=3D libgomp Summary =3D=3D=3D # of expected passes 3 # of unexpected failures 1 The error is: Program received signal SIGSEGV: Segmentation fault - invalid memory refere= nce. Backtrace for this error: #0 0x3fffb7f80477 in ??? #1 0x3fffb799af24 in __GI___libc_free at /usr/src/debug/glibc-2.17-c758a686/malloc/malloc.c:2941 #2 0x3fffb7b9940f in omp_free at /home/seurer/gcc/git/gcc-test2/libgomp/allocator.c:391 #3 0x100015bb in ??? #4 0x10001793 in ??? #5 0x3fffb7927ceb in generic_start_main at ../csu/libc-start.c:266 FAIL: libgomp.fortran/alloc-2.F90 -O execution test If I run just the 32 or the 64 bit ones individually they work: make -k check-target-libgomp RUNTESTFLAGS=3D"--target_board=3Dunix'{-m32}' fortran.exp=3Dlibgomp.fortran/alloc-2.F90" =3D=3D=3D libgomp tests =3D=3D=3D Running target unix/-m32 =3D=3D=3D libgomp Summary =3D=3D=3D # of expected passes 2 make -k check-target-libgomp RUNTESTFLAGS=3D"--target_board=3Dunix'{-m64}' fortran.exp=3Dlibgomp.fortran/alloc-2.F90" =3D=3D=3D libgomp tests =3D=3D=3D Running target unix/-m64 =3D=3D=3D libgomp Summary =3D=3D=3D # of expected passes 2 If I run the 64 bit one before the 32 bit one they both work. If I do the = 64 bit one twice the second run fails. If I do the 32 bit one twice they both work. So, it looks like something is not being cleaned up between the runs that causes the second run to fail if it is a 64 bit run.=