public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113026] Bogus -Wstringop-overflow warning on simple memcpy type loop
Date: Fri, 15 Dec 2023 13:10:19 +0000	[thread overview]
Message-ID: <bug-113026-4-h3UIqnQ7Rb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113026-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from avieira at gcc dot gnu.org ---
Drive by comments as it's been a while since I looked at this. I'm also
surprised we didn't adjust the bounds. But why do we only subtract VF? Like you
say, if there's no loop around edge, can't we guarantee the epilogue will only
need to iterate at most VF-1?  This is assuming we didn't take an early exit,
if we do then we can't assume anything as the iterations 'reset'.

  parent reply	other threads:[~2023-12-15 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 21:42 [Bug tree-optimization/113026] New: " bergner at gcc dot gnu.org
2023-12-14 21:47 ` [Bug tree-optimization/113026] " pinskia at gcc dot gnu.org
2023-12-15  9:24 ` rguenth at gcc dot gnu.org
2023-12-15 10:20 ` rguenth at gcc dot gnu.org
2023-12-15 13:10 ` avieira at gcc dot gnu.org [this message]
2023-12-18  7:14 ` rguenther at suse dot de
2024-01-08 13:52 ` cvs-commit at gcc dot gnu.org
2024-01-08 13:54 ` rguenth at gcc dot gnu.org
2024-01-09 12:37 ` cvs-commit at gcc dot gnu.org
2024-01-20 18:38 ` 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-113026-4-h3UIqnQ7Rb@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).