public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106093] [12/13 Regression] False positive -Wstringop-overflow with -O3 when resizing std::vector
Date: Mon, 16 Jan 2023 13:17:34 +0000	[thread overview]
Message-ID: <bug-106093-4-4zebdZvs5c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106093-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106093

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> Afterwards, we would actually construct the new element in the new storage,
> but the warning happens while just copying the elements from the old storage
> to the new.

Actually we already created the new element first (vector.tcc:668) and then we
copy the old elements (vector.tcc:676).

Either way, it's correct that the loop copying the old elements uses the old
size.

  parent reply	other threads:[~2023-01-16 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 21:31 [Bug c++/106093] New: [Regression] " aclopte at gmail dot com
2023-01-16 10:53 ` [Bug tree-optimization/106093] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-16 13:14 ` redi at gcc dot gnu.org
2023-01-16 13:17 ` redi at gcc dot gnu.org [this message]
2023-05-08 12:24 ` [Bug tree-optimization/106093] [12/13/14 " rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106093-4-4zebdZvs5c@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).