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 C51CF3857031; Thu,  1 Jun 2023 08:37:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C51CF3857031
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685608646;
	bh=UgBT3SUByTmGwBHeKUSAMGWjrHTy5UIn69SALZfFlaE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mOxhVw7DeM7dUVqI0k3FM2IKzHIUHYXtzD7cIQvhumB3sHOFn4tmNRI3FzhPbSe79
	 o9m829yxS72KqiA/z3pWgRCFsIULKqqAp9jknh/DdwkTFjhQIHXm+FtpQ3Re1IfIJ6
	 mLf+K79Fz69ICh+GJXzW8r6I6iCtlrCAqB4wFBfw=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110060] Adding optimizer hints to std::vector
 causes a new -Wstringop-overread false positive
Date: Thu, 01 Jun 2023 08:37:25 +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: 14.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: 
Message-ID: <bug-110060-4-rbedmLmAaM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110060-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=3D110060

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The library change also caused:

FAIL: g++.dg/pr104547.C -std=3Dgnu++17 scan-tree-dump-not vrp2
"_M_default_append"

So I'm definitely changing std::vector again. I don't know if this is worth
keeping open as a tree-optimization bug, or just blame the increased functi=
on
sizes in the library code.=