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/97521] [11 Regression] wrong code with -mno-sse2 since r11-3394 Date: Fri, 23 Oct 2020 07:06:20 +0000 [thread overview] Message-ID: <bug-97521-4-pLg8nP2rd1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97521-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97521 --- Comment #20 from Richard Biener <rguenth at gcc dot gnu.org> --- So at least the tree.c use of get_mask_mode only passes it MODE_VECTOR so we don't have to second-guess the component size when passed a MODE_INT used as representation for an integer vector type. So I'm testing the following tree build_truth_vector_type_for_mode (poly_uint64 nunits, machine_mode mask_mode) { gcc_assert (mask_mode != BLKmode); unsigned HOST_WIDE_INT esize; if (VECTOR_MODE_P (mask_mode)) { poly_uint64 vsize = GET_MODE_BITSIZE (mask_mode); esize = vector_element_size (vsize, nunits); } else esize = 1; tree bool_type = build_nonstandard_boolean_type (esize); return make_vector_type (bool_type, nunits, mask_mode); }
next prev parent reply other threads:[~2020-10-23 7:06 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-21 16:27 [Bug target/97521] New: [11 Regression] wrong code with -mno-sse2 zsojka at seznam dot cz 2020-10-21 16:37 ` [Bug target/97521] [11 Regression] wrong code with -mno-sse2 since r11-3394 jakub at gcc dot gnu.org 2020-10-21 16:56 ` jakub at gcc dot gnu.org 2020-10-21 17:07 ` jakub at gcc dot gnu.org 2020-10-21 18:33 ` marxin at gcc dot gnu.org 2020-10-22 7:19 ` rguenth at gcc dot gnu.org 2020-10-22 7:25 ` jakub at gcc dot gnu.org 2020-10-22 8:32 ` crazylht at gmail dot com 2020-10-22 8:45 ` rguenther at suse dot de 2020-10-22 8:52 ` jakub at gcc dot gnu.org 2020-10-22 8:58 ` jakub at gcc dot gnu.org 2020-10-22 9:00 ` crazylht at gmail dot com 2020-10-22 9:01 ` jakub at gcc dot gnu.org 2020-10-22 9:50 ` rguenther at suse dot de 2020-10-22 10:59 ` cvs-commit at gcc dot gnu.org 2020-10-22 11:11 ` rguenth at gcc dot gnu.org 2020-10-23 6:04 ` rguenth at gcc dot gnu.org 2020-10-23 6:21 ` rguenth at gcc dot gnu.org 2020-10-23 6:23 ` cvs-commit at gcc dot gnu.org 2020-10-23 6:58 ` rguenth at gcc dot gnu.org 2020-10-23 7:00 ` rguenth at gcc dot gnu.org 2020-10-23 7:06 ` rguenth at gcc dot gnu.org [this message] 2020-10-23 8:28 ` ams at gcc dot gnu.org 2020-10-23 8:47 ` ams at gcc dot gnu.org 2020-10-26 11:28 ` cvs-commit at gcc dot gnu.org 2020-10-26 11:28 ` rguenth 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-97521-4-pLg8nP2rd1@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).