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 620B2384AB59; Mon, 22 Apr 2024 19:21:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 620B2384AB59
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1713813711;
	bh=XRv+YzB/h/x0OSIzpNzHGfaHPfA79qZM5Xk5G1egoYw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pGSVdYdKS7g1MdIJACC9KBHcfT0GbNVRU1dBAeNsonMRzntjnaz3wY5QePPFYZQfc
	 T+nZjdhJhWbXtOFAUaOaeYfvQpmRvkSItLjYxgbg4E44vyYh+EUrIcmoGEA6SIhFaN
	 R7S3hYsV7m6OJeJJejBR+uK11uCZwkMXANlf2aEk=
From: "kees at outflux dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109071] -Warray-bounds false positive
 warnings due to code duplication from jump threading
Date: Mon, 22 Apr 2024 19:21:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kees at outflux dot net
X-Bugzilla-Status: NEW
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-109071-4-2J6f1hPwI4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109071-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=3D109071

--- Comment #6 from Kees Cook <kees at outflux dot net> ---
(In reply to qinzhao from comment #5)
> adding __attribute__ ((noreturn)) to the routine "warn" can eliminate the
> false positive warning.

But it does return... it's not an assert.=