public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109804] [11 Regression] internal compiler error in gimple-ssa-warn-access.cc
Date: Wed, 08 May 2024 17:16:47 +0000	[thread overview]
Message-ID: <bug-109804-4-CYYzMeJYs8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109804-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11/12 Regression] internal |[11 Regression] internal
                   |compiler error in           |compiler error in
                   |gimple-ssa-warn-access.cc   |gimple-ssa-warn-access.cc
      Known to fail|                            |13.2.0
      Known to work|                            |12.3.1

--- Comment #17 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Backported the fix to GCC 12 branch too. GCC 11 requires a different patch so
leaving it open if someone wants it fixed there.

      parent reply	other threads:[~2024-05-08 17:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 20:55 [Bug c++/109804] New: " christian.prochaska@genode-labs.com
2023-05-10 20:56 ` [Bug c++/109804] " christian.prochaska@genode-labs.com
2023-05-10 20:59 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org
2023-05-10 21:02 ` mpolacek at gcc dot gnu.org
2023-05-10 21:13 ` [Bug tree-optimization/109804] " pinskia at gcc dot gnu.org
2023-05-10 21:13 ` pinskia at gcc dot gnu.org
2023-05-10 21:14 ` pinskia at gcc dot gnu.org
2023-05-10 21:16 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-05-10 21:17 ` pinskia at gcc dot gnu.org
2023-05-10 21:18 ` pinskia at gcc dot gnu.org
2023-05-10 21:48 ` mpolacek at gcc dot gnu.org
2023-05-11  6:30 ` rguenth at gcc dot gnu.org
2023-05-29 10:08 ` jakub at gcc dot gnu.org
2024-02-21  7:23 ` pinskia at gcc dot gnu.org
2024-02-22 17:29 ` cvs-commit at gcc dot gnu.org
2024-02-22 17:30 ` [Bug tree-optimization/109804] [11/12/13 " pinskia at gcc dot gnu.org
2024-02-22 21:13 ` cvs-commit at gcc dot gnu.org
2024-02-22 21:13 ` [Bug tree-optimization/109804] [11/12 " pinskia at gcc dot gnu.org
2024-05-08 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-08 17:16 ` pinskia at gcc dot gnu.org [this message]

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-109804-4-CYYzMeJYs8@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).