public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100885] [12 Regression] ICE: in extract_constrain_insn, at recog.c:2671: insn does not satisfy its constraints: {sse4_1_zero_extendv8qiv8hi2} Date: Mon, 07 Jun 2021 14:59:14 +0000 [thread overview] Message-ID: <bug-100885-4-LZIF4rUe3c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100885-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100885 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:bcb5e97899e324c092806b49256a515593268a54 commit r11-8518-gbcb5e97899e324c092806b49256a515593268a54 Author: H.J. Lu <hjl.tools@gmail.com> Date: Mon Jun 7 07:29:31 2021 -0700 x86: Update g++.target/i386/pr100885.C Since long is 32 bits for x32, update g++.target/i386/pr100885.C to cast __m64 to long long for x32. PR target/100885 * g++.target/i386/pr100885.C (_mm_set_epi64): Cast __m64 to long long. (cherry picked from commit 52730540e83c81ee595a51feb7736ff753c98139)
prev parent reply other threads:[~2021-06-07 14:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 20:51 [Bug target/100885] New: " zsojka at seznam dot cz 2021-06-03 3:33 ` [Bug target/100885] " crazylht at gmail dot com 2021-06-03 3:49 ` crazylht at gmail dot com 2021-06-03 5:10 ` crazylht at gmail dot com 2021-06-03 7:14 ` crazylht at gmail dot com 2021-06-03 10:40 ` crazylht at gmail dot com 2021-06-07 3:28 ` cvs-commit at gcc dot gnu.org 2021-06-07 4:38 ` cvs-commit at gcc dot gnu.org 2021-06-07 4:41 ` crazylht at gmail dot com 2021-06-07 9:04 ` rguenth at gcc dot gnu.org 2021-06-07 14:49 ` cvs-commit at gcc dot gnu.org 2021-06-07 14:59 ` cvs-commit at gcc dot gnu.org [this message]
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-100885-4-LZIF4rUe3c@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).