From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 802B83858416; Thu, 21 Oct 2021 14:09:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 802B83858416 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/102838] [12 regression] Several tests SEGV in gomp_loop_ull_init Date: Thu, 21 Oct 2021 14:09:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: Thu, 21 Oct 2021 14:09:26 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102838 --- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE Uni-Bielefeld.DE> --- >> --- Comment #5 from Jakub Jelinek --- >> Does the committed patch fix the issue on Solaris? > > I'll see after tonight's bootstrap. The original one attached to the PR > fixed only a few of the failures: > > -FAIL: libgomp.c/../libgomp.c-c++-common/for-1.c execution test > > -FAIL: libgomp.c/../libgomp.c-c++-common/for-2.c execution test > > -FAIL: libgomp.c/../libgomp.c-c++-common/for-7.c execution test > -FAIL: libgomp.c/../libgomp.c-c++-common/for-8.c execution test The committed version is the same: quite a number of the previous failures remain. E.g. even with OMP_NUM_THREADS=3D8, for-3.c starts a large number of threads (200+), then hangs under gdb, but if I let it run directly, it SEGVs again and the core dump shows the same unaligned access (with dbx, gdb cannot interpret the core dump): t@198 (l@198) terminated by signal SEGV (no mapping at the fault address) 0xfe5d7fb8: gomp_loop_ull_guided_start+0x01a8: movaps %xmm0,0x00000010(%= esi) (dbx) print $esi=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 $esi =3D 134981864=