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 6371F3858416; Fri, 26 Apr 2024 08:42:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6371F3858416
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1714120933;
	bh=M+RzNBtTs9dHw/5aDFt+Wz7fkJSe1TNxDBz7GpHV8DI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=NyxLSVJfkfy+PDDYhDT3p/ARqKuEcOz9j1ZFRIe+3BG0VqY2EFEjOILPBYotp2nsc
	 7Lda3B905/g3rB1U9d/33ybXoY8uT88NJdNV7OYfjOEZbbfGd7mGTildgEazDYdkpD
	 PNYZmHHYn7vuFqECtsmxVgML7LtrCJ3HEJqH0RlU=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/113867] [14 Regression][OpenMP] Wrong code with mapping
 pointers in structs
Date: Fri, 26 Apr 2024 08:42:12 +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: 14.0
X-Bugzilla-Keywords: openmp, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: burnus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-113867-4-SPYvQnmETn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113867-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=3D113867

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P2

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Per IRC discussions downgrading this to P2, it isn't something used widely =
in
real-world code and while we can get some partial fix soon, a full fix will
take likely longer.  If it is fixed relatively soon in stage1, we can consi=
der
backporting the non-risky parts of the fixes to 14.2.=