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 315563858029; Tue, 12 Mar 2024 13:22:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 315563858029
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1710249756;
	bh=gPS6G0H0xJ6OCGd/5G8Sw0SvF0/OlyeZn8AGd3silqE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=HoIH71Fm1FR78IQCr6ee0+fwU0NpKz5UQ9pAp+jjnKOzR0DkoUXRsqq6QwaVnh4Xg
	 n+mMA36676XVANyhnOkpsjBp7F1vttNVSmEMD9hBJdPphrzxOEs9AdVo7A+KsEXtiT
	 s6F1QcC9JV7wYRAq/JDYVtvnriUlbgZJr9kSCGKw=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/112709] [13/14 Regression] address sanitize and
 returns_twice causes an ICE
Date: Tue, 12 Mar 2024 13:22:35 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-112709-4-QkY0Myfix9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112709-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112709-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=3D112709

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

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 13.{1,2} has been released with this bug, so P2.=