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 51C2E3858C62; Thu,  1 Feb 2024 06:17:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 51C2E3858C62
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706768268;
	bh=GjQrFkEla6RVUQpgfNT/bWq2GvoneUL9WWnsHQK734M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=HtlerlwW71tS7JTUZ2MX+042uefvQuooWwbUMsdaFcFErOvTtp2vQpJgYK2Ykaftp
	 V8sZq38g8RfPbReVdghVebDRcUxDtrgRK8co8SDsrNCGxD7QwpJsj51fUQiszG/SqN
	 yfD9fE7Ue4aaXxc6Llq+2pWLeoR4I5QmKtvXIk2M=
From: "panchenghui at loongson dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111403] LoongArch: Wrong code with -O -mlasx
 -fopenmp-simd
Date: Thu, 01 Feb 2024 06:17:46 +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: panchenghui at loongson dot cn
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: <bug-111403-4-AdekluHE3v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111403-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111403-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #8 from Chenghui Pan <panchenghui at loongson dot cn> ---
(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...

After applying this commit, GCC does not apply loop peeling while processing
the openmp reduction directive, which I think is the spawn point of the
problematic codes (According to Guo Jie's sample).=