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 ipa/101625] [11/12 Regression] ICE in modref_tree<int>::merge with LTO and -m32
Date: Tue, 27 Jul 2021 11:03:20 +0000	[thread overview]
Message-ID: <bug-101625-4-2SU4gMd1dv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101625-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org
   Target Milestone|---                         |11.2
          Component|lto                         |ipa
            Summary|ICE in                      |[11/12 Regression] ICE in
                   |modref_tree<int>::merge     |modref_tree<int>::merge
                   |with LTO and -m32           |with LTO and -m32
           Priority|P3                          |P2
           Keywords|                            |ice-on-valid-code, lto

  reply	other threads:[~2021-07-27 11:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 16:45 [Bug lto/101625] New: " tonyb at cybernetics dot com
2021-07-27 11:03 ` rguenth at gcc dot gnu.org [this message]
2021-07-28  7:07 ` [Bug ipa/101625] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-08-02 14:07 ` [Bug ipa/101625] [11/12 Regression] ICE in modref_tree<int>::merge with LTO and -m32 since r11-3825-g71dbabccbfb295c8 marxin at gcc dot gnu.org
2021-08-05 11:43 ` marxin at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` [Bug ipa/101625] [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-101625-4-2SU4gMd1dv@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).