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 target/89270] [11/12/13 regression] AVR ICE: verify_gimple failed
Date: Tue, 05 Dec 2023 07:37:50 +0000	[thread overview]
Message-ID: <bug-89270-4-j9MVARkJih@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89270-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|rguenth at gcc dot gnu.org         |unassigned at gcc dot gnu.org
      Known to work|                            |14.0
             Status|ASSIGNED                    |NEW
            Summary|[11/12/13/14 regression]    |[11/12/13 regression] AVR
                   |AVR ICE: verify_gimple      |ICE: verify_gimple failed
                   |failed                      |
          Component|c                           |target

--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.  Joseph correctly mentioned that iff AVR would define
__int24 using INT_N in avr-modes.def the issue would have been mitigated as
well
(that's a comparatively "modern" way of registering additional integer types).

So it's really also a target issue.

I'm not planning to backport this frontend change given a more targeted fix
would be available.

      parent reply	other threads:[~2023-12-05  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89270-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug middle-end/89270] [9/10 " jakub at gcc dot gnu.org
2021-06-01  8:13 ` [Bug middle-end/89270] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:40 ` [Bug middle-end/89270] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:36 ` jakub at gcc dot gnu.org
2023-07-07 10:34 ` [Bug middle-end/89270] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-12-03 21:59 ` pinskia at gcc dot gnu.org
2023-12-04 13:03 ` rguenth at gcc dot gnu.org
2023-12-05  7:35 ` [Bug c/89270] " cvs-commit at gcc dot gnu.org
2023-12-05  7:37 ` rguenth 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-89270-4-j9MVARkJih@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).