public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92955] [10 regression] False positive stringop-overflow warning with vectorization and loop unrolling
Date: Fri, 20 Mar 2020 22:10:29 +0000	[thread overview]
Message-ID: <bug-92955-4-nHMVJJtNyj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92955-4@http.gcc.gnu.org/bugzilla/>

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

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|10.0                        |11.0

--- Comment #10 from Jeffrey A. Law <law at redhat dot com> ---
Certainly.  So ISTM this is punt to gcc-11 (and likely beyond) and hope that
one day we can do better at determining some of the unrolled iterations can't
actually happen at runtime and can be removed.

  parent reply	other threads:[~2020-03-20 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92955-4@http.gcc.gnu.org/bugzilla/>
2020-03-20  8:58 ` rguenth at gcc dot gnu.org
2020-03-20 22:10 ` law at redhat dot com [this message]
2021-01-14  8:21 ` [Bug tree-optimization/92955] [10/11 " rguenth at gcc dot gnu.org
2021-04-27 11:38 ` [Bug tree-optimization/92955] [10/11/12 " jakub at gcc dot gnu.org
2021-07-28  7:04 ` rguenth at gcc dot gnu.org
2022-04-21  7:47 ` rguenth at gcc dot gnu.org
2023-05-29 10:02 ` [Bug tree-optimization/92955] [10/11/12/13/14 " jakub 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-92955-4-nHMVJJtNyj@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).