public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103928] [12 Regression] ICE in get_insn_template, at final.c:2050
Date: Thu, 06 Jan 2022 10:09:38 +0000 [thread overview]
Message-ID: <bug-103928-4-j3GOy1aA9j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103928-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103928
--- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Martin Liška from comment #6)
> Then you may be affected by PR103905 which is fixed on the current master.
> Please pull to tip of master branch.
No, bdver4 does not include XOP.
next prev parent reply other threads:[~2022-01-06 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 9:01 [Bug c/103928] New: [12] " manuel.lauss at googlemail dot com
2022-01-06 9:12 ` [Bug target/103928] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-06 9:45 ` jakub at gcc dot gnu.org
2022-01-06 9:58 ` marxin at gcc dot gnu.org
2022-01-06 9:59 ` manuel.lauss at googlemail dot com
2022-01-06 10:01 ` marxin at gcc dot gnu.org
2022-01-06 10:06 ` manuel.lauss at googlemail dot com
2022-01-06 10:08 ` marxin at gcc dot gnu.org
2022-01-06 10:09 ` ubizjak at gmail dot com [this message]
2022-01-06 10:20 ` marxin at gcc dot gnu.org
2022-01-06 10:58 ` manuel.lauss at googlemail dot com
2022-01-06 12:02 ` manuel.lauss at googlemail dot com
2022-01-06 16:50 ` ubizjak at gmail dot com
2022-01-06 17:02 ` ubizjak at gmail dot com
2022-01-06 18:53 ` manuel.lauss at googlemail dot com
2022-01-06 21:26 ` 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-103928-4-j3GOy1aA9j@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).