public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110926] [14 regression] Bootstrap failure (matmul_i1.c:1781:1: internal compiler error: RTL check: expected elt 0 type 'i' or 'n', have 'w' (rtx const_int) in vpternlog_redundant_operand_mask, at config/i386/i386.cc:19460) Date: Mon, 07 Aug 2023 05:30:27 +0000 [thread overview] Message-ID: <bug-110926-4-fu1spykhD1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110926-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110926 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #7 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Thanks for identifying the problem. Please don't rename the argument to 'op_mask' though: the parameter itself is not a mask, it's an eight-bit control word of the vpternlog instruction (holding the logic table of a three-operand Boolean function). The function derives a three-bit mask from it.
next prev parent reply other threads:[~2023-08-07 5:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-07 1:56 [Bug bootstrap/110926] New: " sjames at gcc dot gnu.org 2023-08-07 1:57 ` [Bug target/110926] " pinskia at gcc dot gnu.org 2023-08-07 1:58 ` pinskia at gcc dot gnu.org 2023-08-07 1:58 ` sjames at gcc dot gnu.org 2023-08-07 2:17 ` sjames at gcc dot gnu.org 2023-08-07 2:45 ` sjames at gcc dot gnu.org 2023-08-07 3:03 ` crazylht at gmail dot com 2023-08-07 3:17 ` crazylht at gmail dot com 2023-08-07 5:30 ` amonakov at gcc dot gnu.org [this message] 2023-08-07 5:51 ` crazylht at gmail dot com 2023-08-07 13:20 ` cvs-commit at gcc dot gnu.org 2023-08-07 13:21 ` crazylht at gmail dot com 2023-08-07 15:31 ` 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-110926-4-fu1spykhD1@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).