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/114249] [14 regression] ICE when building lvm2-2.03.22 (error: invalid types in nop conversion)
Date: Wed, 06 Mar 2024 02:44:16 +0000	[thread overview]
Message-ID: <bug-114249-4-Eyiqb06psM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114249-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.0
           Keywords|                            |ice-on-valid-code
                 CC|                            |pinskia at gcc dot gnu.org

  reply	other threads:[~2024-03-06  2:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  2:33 [Bug tree-optimization/114249] New: " sjames at gcc dot gnu.org
2024-03-06  2:44 ` pinskia at gcc dot gnu.org [this message]
2024-03-06  2:46 ` [Bug tree-optimization/114249] " pinskia at gcc dot gnu.org
2024-03-06  3:03 ` sjames at gcc dot gnu.org
2024-03-06  3:06 ` pinskia at gcc dot gnu.org
2024-03-06  3:39 ` sjames at gcc dot gnu.org
2024-03-06  8:08 ` rguenth at gcc dot gnu.org
2024-03-06  8:28 ` rguenth at gcc dot gnu.org
2024-03-06  9:27 ` cvs-commit at gcc dot gnu.org
2024-03-06  9:28 ` rguenth at gcc dot gnu.org
2024-03-06 12:01 ` rguenth at gcc dot gnu.org
2024-03-06 18:37 ` patrick at rivosinc dot com

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-114249-4-Eyiqb06psM@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).