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 27A333858D38; Tue,  6 Feb 2024 07:51:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 27A333858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707205912;
	bh=0dnWT82K3RCMNYtOQGIWZpK9bEwYyPi83d2TnoFx72U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JERVBAuokky12h/qPYpiKdUzgNgaCPZ5QlLLcpkfveiBoA7uFvHhZHhQNL8nuJj3l
	 z+aSqLbn3nU3JPnmkCQ4Nj2AX8vielgKAN+2dnDCaBDK/NkktnC/or1TKpM70cfRXr
	 aH92U2xqcwwbtfRsy+v2KfSBKi6GfVZEU4D98YL0=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113775] Bogus Wstringop-overflow in
 __atomic_load_n combined with sanitizer flags
Date: Tue, 06 Feb 2024 07:51: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.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords
Message-ID: <bug-113775-4-clGjb24a90@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113775-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=3D113775

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah, the

'cc1plus: note: destination object is likely at address zero'

message hints at that we likely diagnose a threaded path where the pointer
is zero.  We were likely inclined to perform the threading by dynamic
checks inserted by the sanitizer.=