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 debug/113481] avr: internal compiler error in decompose, at rtl.h:2298 Date: Thu, 18 Jan 2024 18:03:42 +0000 [thread overview] Message-ID: <bug-113481-4-qxLkPoimAG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113481-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113481 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[14 Regession] avr: |avr: internal compiler |internal compiler error in |error in decompose, at |decompose, at rtl.h:2298 |rtl.h:2298 Keywords| |ice-checking Target Milestone|14.0 |--- --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note -fchecking does not enable gcc_checking_assert checking so you will need to configure older compilers with --enable-checking=yes to get the assert hitting. The assert that hits: gcc_checking_assert (INTVAL (x.first) == sext_hwi (INTVAL (x.first), precision) || (x.second == BImode && INTVAL (x.first) == 1)); What this assert is trying to make a point of is that we always sign extend CONST_INT to HostWideInt (almost always 64bit integer) from the precision of the mode.
next prev parent reply other threads:[~2024-01-18 18:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 13:52 [Bug debug/113481] New: " gjl at gcc dot gnu.org 2024-01-18 13:54 ` [Bug debug/113481] [14 Regession] " gjl at gcc dot gnu.org 2024-01-18 13:58 ` gjl at gcc dot gnu.org 2024-01-18 14:22 ` rguenth at gcc dot gnu.org 2024-01-18 18:03 ` pinskia at gcc dot gnu.org [this message] 2024-01-18 18:32 ` [Bug debug/113481] " gjl at gcc dot gnu.org 2024-01-18 19:08 ` gjl at gcc dot gnu.org 2024-01-18 20:57 ` gjl at gcc dot gnu.org 2024-01-18 22:22 ` [Bug middle-end/113481] " pinskia at gcc dot gnu.org 2024-01-18 22:23 ` [Bug debug/113481] " pinskia at gcc dot gnu.org 2024-01-18 22:30 ` pinskia at gcc dot gnu.org 2024-01-18 22:33 ` pinskia 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-113481-4-qxLkPoimAG@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: linkBe 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).