public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105679] [12 Regression] extra -Warray-bounds warning added with -fsanitize=shift due to jump threading
Date: Fri, 07 Oct 2022 06:57:21 +0000	[thread overview]
Message-ID: <bug-105679-4-ZDq5DjBtnk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105679-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Kees Cook from comment #9)
> Does anyone have some time to do this backport for GCC 12?

I sofar refrained from doing this because of the large amount of fallout and
followup changes and I think those are not warranted on the GCC 12 branch.

  parent reply	other threads:[~2022-10-07  6:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  0:32 [Bug c/105679] New: erroneous -Warray-bounds warning with sanitizer kees at outflux dot net
2022-05-21  0:33 ` [Bug c/105679] " kees at outflux dot net
2022-05-21  1:02 ` [Bug tree-optimization/105679] " pinskia at gcc dot gnu.org
2022-05-23  6:50 ` [Bug tree-optimization/105679] [12/13 Regression] extra -Warray-bounds warning added with -fsanitize=shift due to jump threading rguenth at gcc dot gnu.org
2022-07-29  8:19 ` rguenth at gcc dot gnu.org
2022-07-29 10:06 ` cvs-commit at gcc dot gnu.org
2022-07-29 10:06 ` [Bug tree-optimization/105679] [12 " rguenth at gcc dot gnu.org
2022-07-30 23:50 ` kees at outflux dot net
2022-08-01  8:01 ` rguenth at gcc dot gnu.org
2022-08-02  6:35 ` rguenth at gcc dot gnu.org
2022-10-06 17:27 ` kees at outflux dot net
2022-10-07  6:57 ` rguenth at gcc dot gnu.org [this message]
2022-10-08  2:31 ` kees at outflux dot net
2023-05-08 12:24 ` 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-105679-4-ZDq5DjBtnk@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).