public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96791] ICE in convert_mode_scalar, at expr.c:412 Date: Wed, 25 Nov 2020 21:12:45 +0000 [thread overview] Message-ID: <bug-96791-4-Wp5WVLKcBx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96791-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791 --- Comment #22 from Michael Meissner <meissner at gcc dot gnu.org> --- When I wrote the original in power7 days, the intent was: If the user said -mcpu=power7 (for 32-bit) and did not explicitly set either -mabi=altivec or -mabi=no-altivec, that -mabi=altivec would be set automagically. If the user said -mcpu=power7 and did specify whether the altivec was set, the compiler would honor that request. For 32-bit, I assume the problem may be our old friend TImode. Other parts of the compiler, including the generic parts of block move assume that there must be an integer mode as large as the largest non-vector mode. We don't provide TImode in 32-bit, and that leads us to have to disable IEEE 128-bit hardware support because we don't have a corresponding 128-bit integer for doing moves. Before OPAQUE we did define OImode and XImode, but never enabled them, and that prevented some ICEs where the machine independent parts did not bother to check if the get integer mode size that is n-bits returned NULL.
next prev parent reply other threads:[~2020-11-25 21:12 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-26 3:33 [Bug target/96791] New: " asolokha at gmx dot com 2020-08-27 18:50 ` [Bug target/96791] " dje at gcc dot gnu.org 2020-08-27 19:24 ` wschmidt at gcc dot gnu.org 2020-08-27 19:38 ` acsawdey at gcc dot gnu.org 2020-08-27 23:21 ` wschmidt at gcc dot gnu.org 2020-08-28 0:58 ` acsawdey at gcc dot gnu.org 2020-08-31 9:28 ` asolokha at gmx dot com 2020-08-31 14:20 ` acsawdey at gcc dot gnu.org 2020-09-02 14:02 ` acsawdey at gcc dot gnu.org 2020-09-09 23:32 ` acsawdey at gcc dot gnu.org 2020-09-11 2:18 ` acsawdey at gcc dot gnu.org 2020-11-17 16:10 ` cvs-commit at gcc dot gnu.org 2020-11-24 2:46 ` asolokha at gmx dot com 2020-11-24 2:47 ` asolokha at gmx dot com 2020-11-25 0:49 ` bergner at gcc dot gnu.org 2020-11-25 1:04 ` segher at gcc dot gnu.org 2020-11-25 1:06 ` segher at gcc dot gnu.org 2020-11-25 3:29 ` asolokha at gmx dot com 2020-11-25 20:10 ` bergner at gcc dot gnu.org 2020-11-25 20:31 ` segher at gcc dot gnu.org 2020-11-25 20:39 ` segher at gcc dot gnu.org 2020-11-25 20:42 ` bergner at gcc dot gnu.org 2020-11-25 21:12 ` meissner at gcc dot gnu.org [this message] 2020-11-25 22:28 ` segher at gcc dot gnu.org 2021-09-02 22:15 ` bergner at gcc dot gnu.org 2021-09-02 22:53 ` segher 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-96791-4-Wp5WVLKcBx@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).