From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ABCB4385840C; Wed, 31 Jan 2024 16:48:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ABCB4385840C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706719732; bh=J44OLwSuoCSeyZaWGAvV1U6HloA3yszkoMgkVvaZTNo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OsJse6BJfYj8A0r5Ji+yNtVRksfWhyOKOHPwbOvBwEyQTq8cdqed6JHCSujeIwUhV RSgnX5qknLUBaDgs54iGmrqC5W2DlU2mk8w+oR30T0qc32PUEC/ZxDW/6T3j8aDXGH nhwmkivmbPptT392oOiIULZ8LcZYDx1pZiy6/wEQ= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111403] LoongArch: Wrong code with -O -mlasx -fopenmp-simd Date: Wed, 31 Jan 2024 16:48:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 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: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111403 --- Comment #5 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #4) > After r14-5545 this issue became latent. >=20 > And at some point before r14-5545 this issue became nondeterministic: a > compiled program *sometimes* crashes. Really strange... At r14-5544, if running the compiled program in GDB it *always* crash, but = if directly running it it *sometimes* crash. What's the difference between GD= B or not?!=