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 target/97532] [11 Regression] Error: insn does not satisfy its constraints, internal compiler error: in extract_constrain_insn, at recog.c:2196 Date: Thu, 22 Oct 2020 16:32:35 +0000 [thread overview] Message-ID: <bug-97532-4-d10oXUw06T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97532-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97532 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Error: insn does not |[11 Regression] Error: insn |satisfy its constraints, |does not satisfy its |internal compiler error: in |constraints, internal |extract_constrain_insn, at |compiler error: in |recog.c:2196 |extract_constrain_insn, at | |recog.c:2196 Last reconfirmed| |2020-10-22 Target Milestone|--- |11.0 Status|UNCONFIRMED |NEW Target| |x86_64-*-* i?86-*-* Ever confirmed|0 |1 Component|libgomp |target --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed.
next prev parent reply other threads:[~2020-10-22 16:32 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 16:12 [Bug libgomp/97532] New: " vries at gcc dot gnu.org 2020-10-22 16:32 ` rguenth at gcc dot gnu.org [this message] 2020-10-22 17:16 ` [Bug target/97532] [11 Regression] " jakub at gcc dot gnu.org 2020-10-22 18:19 ` jakub at gcc dot gnu.org 2020-10-22 18:48 ` vmakarov at gcc dot gnu.org 2020-10-22 19:03 ` jakub at gcc dot gnu.org 2020-10-23 5:49 ` crazylht at gmail dot com 2020-10-23 7:42 ` jakub at gcc dot gnu.org 2020-10-23 8:11 ` crazylht at gmail dot com 2020-10-23 15:21 ` vmakarov at gcc dot gnu.org 2020-10-27 6:05 ` crazylht at gmail dot com 2020-10-28 9:40 ` rguenth at gcc dot gnu.org 2020-10-29 12:36 ` vries at gcc dot gnu.org 2020-10-30 0:54 ` crazylht at gmail dot com 2020-11-04 5:07 ` cvs-commit at gcc dot gnu.org 2020-11-04 5:13 ` crazylht at gmail dot com 2020-11-18 15:45 ` 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-97532-4-d10oXUw06T@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).