public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "evan.teran at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114178] incorrect -Wstringop-overflow with freestanding + new w/ initialization + no sse
Date: Thu, 29 Feb 2024 23:03:37 +0000	[thread overview]
Message-ID: <bug-114178-4-D4n6UrGLKj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114178-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Evan Teran <evan.teran at gmail dot com> ---
@Andrew, thanks for the quick analysis! Just to confirm, the warning is in fact
incorrect and the emitted code is not stomping outside of the buffer bounds?

I ask because I did also one last bit, which is that changing the buffer size
can make the warning go away. That is if I make the buffer in the example
something like 132, then it's happy again, which at the very least, makes me
wonder if the vectorized code is in fact going out of bounds when the size
doesn't align with the vectorized code's expectations.

  parent reply	other threads:[~2024-02-29 23:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 22:04 [Bug c++/114178] New: incorrect -Wstringop-overflow with freestanding + placement " evan.teran at gmail dot com
2024-02-29 22:18 ` [Bug tree-optimization/114178] incorrect -Wstringop-overflow with freestanding + " pinskia at gcc dot gnu.org
2024-02-29 22:18 ` pinskia at gcc dot gnu.org
2024-02-29 22:20 ` pinskia at gcc dot gnu.org
2024-02-29 23:03 ` evan.teran at gmail dot com [this message]
2024-02-29 23:15 ` pinskia 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-114178-4-D4n6UrGLKj@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).