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 542473858D33; Thu, 11 May 2023 09:47:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 542473858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683798455;
	bh=t5HHhwsmCBHFDoSzDn44jxBONvxGKB6kYbx8HIKuHzA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=nKZ4F9m8fSzVzEZmY/GJFgbFdFU97HW9rhHDkPxTZCtPHmNY+j1/JZNE9I0pGV7C/
	 mfv1ZKv4wVlyqAtqdm11SkZApOpfwLSzpiukMcRKrLo1WUI5IWS5DdVhe0cSnSAJGV
	 GSGgMmimN6K62C2NbYkikBwysmfjsy4nYmWIkgKQ=
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109791] -Wstringop-overflow warning with -O3
 and _GLIBCXX_USE_CXX11_ABI=0
Date: Thu, 11 May 2023 09:47:34 +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: 12.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aldyh at gcc dot gnu.org
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-109791-4-b1TmiA7NA8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109791-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=3D109791

--- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---

> but the issue with the PHI node remains unless we sink the &str part
> (but there's many uses of __i_14).  I guess it's still the "easiest"
> way to get rangers help.  Aka make
>=20
>  # __i_14' =3D PHI <1(10), 2(9)>
>  __i_14 =3D &str + __i_14'; // would be a POINTER_PLUS_EXPR
>=20
> it's probably still not a complete fix but maybe a good start.  Of course
> it increases the number of stmts - &MEM[&str + 1B] was an 'invariant'
> (of course the PHI result isn't).  There's not a good place for this
> transform - we never "fold" PHIs (and this would be an un-folding).

Ughh, that sucks.  Let's see if Andrew has any ideas, but on my end I won't=
 be
able to work on prange until much later this cycle-- assuming I finish what=
 I
have on my plate.=