public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108272] [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:339
Date: Mon, 09 Jan 2023 18:42:19 +0000 [thread overview]
Message-ID: <bug-108272-4-ZEVSevVJet@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108272-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108272
--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Kewen Lin from comment #2)
> Created attachment 54192 [details]
> untested patch
>
> Hi @Arseny, I hope this patch can help to clear all the ICEs about
> unexpected uses of MMA opaque types in inline asm, that is to filter those
> noises duplicated to this bug.
Indeed, I haven't seen such ICEs w/ the patch applied so far. Still get an ICE
in gen_movoo, at config/rs6000/mma.md:292 when compiling
gcc/testsuite/gcc.target/powerpc/pr96506-1.c w/ -m32, though. Do you want me to
file another PR for that one?
next prev parent reply other threads:[~2023-01-09 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 6:55 [Bug target/108272] New: " asolokha at gmx dot com
2023-01-03 7:04 ` [Bug target/108272] " linkw at gcc dot gnu.org
2023-01-05 6:53 ` linkw at gcc dot gnu.org
2023-01-09 18:42 ` asolokha at gmx dot com [this message]
2023-01-10 2:06 ` linkw at gcc dot gnu.org
2023-01-10 3:00 ` asolokha at gmx dot com
2023-01-16 8:17 ` cvs-commit at gcc dot gnu.org
2023-02-13 2:03 ` cvs-commit at gcc dot gnu.org
2023-02-13 2:09 ` cvs-commit at gcc dot gnu.org
2023-02-13 2:18 ` cvs-commit at gcc dot gnu.org
2023-02-13 2:25 ` linkw 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-108272-4-ZEVSevVJet@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).