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 tree-optimization/94727] [10 Regression] GCC produces incorrect code with -O3 since r10-5071-g02d895504cc59be0 Date: Tue, 28 Apr 2020 07:04:43 +0000 [thread overview] Message-ID: <bug-94727-4-38EGO1GUj1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94727-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94727 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:e62a820d686d1fa97a9eefdc65ca07d8f96ac9f4 commit r10-8006-ge62a820d686d1fa97a9eefdc65ca07d8f96ac9f4 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Tue Apr 28 08:04:29 2020 +0100 vect: Fix COND_EXPRs involving variant booleans [PR94727] The previous patch for this PR handled separate comparisons. However, as arm targets show, the same fix is needed when handling comparisons embedded in a VEC_COND_EXPR. Here too, the problem is that vect_get_constant_vectors will calculate its own vector type, using truth_type_for on the STMT_VINFO_VECTYPE, and the vectoriable_* routines need to be consistent with that. 2020-04-28 Richard Sandiford <richard.sandiford@arm.com> gcc/ PR tree-optimization/94727 * tree-vect-stmts.c (vect_is_simple_cond): If both comparison operands are invariant booleans, use the mask type associated with the STMT_VINFO_VECTYPE. Use !slp_node instead of !vectype to exclude SLP. (vectorizable_condition): Pass vectype unconditionally to vect_is_simple_cond.
prev parent reply other threads:[~2020-04-28 7:04 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-23 5:14 [Bug tree-optimization/94727] New: GCC produces incorrect code with -O3 vsevolod.livinskij at frtk dot ru 2020-04-23 5:35 ` [Bug tree-optimization/94727] [10 Regression] GCC produces incorrect code with -O3 since r10-5071-g02d895504cc59be0 marxin at gcc dot gnu.org 2020-04-23 6:44 ` rguenth at gcc dot gnu.org 2020-04-23 7:02 ` rguenth at gcc dot gnu.org 2020-04-23 7:34 ` rsandifo at gcc dot gnu.org 2020-04-23 10:26 ` rsandifo at gcc dot gnu.org 2020-04-23 12:35 ` rguenth at gcc dot gnu.org 2020-04-23 13:02 ` rsandifo at gcc dot gnu.org 2020-04-23 14:45 ` cvs-commit at gcc dot gnu.org 2020-04-23 14:48 ` rsandifo at gcc dot gnu.org 2020-04-28 7:04 ` 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-94727-4-38EGO1GUj1@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).