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 middle-end/113988] during GIMPLE pass: bitintlower: internal compiler error: in lower_stmt, at gimple-lower-bitint.cc:5470
Date: Mon, 19 Feb 2024 14:22:20 +0000	[thread overview]
Message-ID: <bug-113988-4-wPXBcOGfOa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113988-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder if we should stop claiming those modes are "supported".  Maybe instead
of making them integer modes they should be OPAQUE_MODE or vector (integer)
modes in the first place?  There's bitwise_mode_for_mode but that will
I think never do anything unless we have MAX_FIXED_MODE_SIZE < OImode?
It will also never make vector modes from integer modes ...

  parent reply	other threads:[~2024-02-19 14:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  9:51 [Bug c++/113988] New: " janschultke at googlemail dot com
2024-02-19 10:00 ` [Bug middle-end/113988] " pinskia at gcc dot gnu.org
2024-02-19 10:01 ` janschultke at googlemail dot com
2024-02-19 10:05 ` jakub at gcc dot gnu.org
2024-02-19 14:22 ` rguenth at gcc dot gnu.org [this message]
2024-02-19 14:30 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` jakub at gcc dot gnu.org
2024-02-19 14:37 ` rguenth at gcc dot gnu.org
2024-02-19 14:39 ` rguenth at gcc dot gnu.org
2024-02-19 14:40 ` jakub at gcc dot gnu.org
2024-02-19 14:42 ` jakub at gcc dot gnu.org
2024-02-19 14:44 ` rguenther at suse dot de
2024-02-19 15:35 ` hjl.tools at gmail dot com
2024-02-19 18:57 ` jakub at gcc dot gnu.org
2024-02-20  7:32 ` rguenth at gcc dot gnu.org
2024-02-20  9:12 ` rsandifo at gcc dot gnu.org
2024-02-21 12:40 ` jakub at gcc dot gnu.org
2024-02-21 12:50 ` jakub at gcc dot gnu.org
2024-02-22  7:47 ` rguenther at suse dot de
2024-02-22  8:10 ` jakub at gcc dot gnu.org
2024-02-22  8:34 ` rguenther at suse dot de
2024-02-22  8:37 ` jakub at gcc dot gnu.org
2024-02-22  8:52 ` rguenther at suse dot de
2024-02-23 10:06 ` jakub at gcc dot gnu.org
2024-02-24 11:46 ` jakub at gcc dot gnu.org
2024-02-25 18:37 ` zsojka at seznam dot cz
2024-02-26 21:41 ` zsojka at seznam dot cz
2024-02-27 11:53 ` jakub at gcc dot gnu.org
2024-02-28  8:55 ` cvs-commit at gcc dot gnu.org
2024-02-28  9:01 ` 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-113988-4-wPXBcOGfOa@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).