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/109721] [14 Regression] predcom-2 started to fail on arc-elf after r14-391 Date: Thu, 04 May 2023 10:52:07 +0000 [thread overview] Message-ID: <bug-109721-4-J3s9xZZ3xq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109721-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109721 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:82cfd93ae81a5687bf2a1b12d964c630e95517a7 commit r14-474-g82cfd93ae81a5687bf2a1b12d964c630e95517a7 Author: Richard Biener <rguenther@suse.de> Date: Thu May 4 10:06:47 2023 +0200 tree-optimization/109721 - emulated vectors When fixing PR109672 I noticed we let SImode AND through when target_support_p even though it isn't word_mode and I didn't want to change that but had to catch the case where SImode PLUS is supported but emulated vectors rely on it being word_mode. The following makes sure to preserve the word_mode check when !target_support_p to avoid excessive lowering later even for bit operations. PR tree-optimization/109721 * tree-vect-stmts.cc (vectorizable_operation): Make sure to test word_mode for all !target_support_p operations.
next prev parent reply other threads:[~2023-05-04 10:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 22:16 [Bug tree-optimization/109721] New: [14 Regression] predcom-2 fails after recent changes law at gcc dot gnu.org 2023-05-03 22:19 ` [Bug tree-optimization/109721] [14 Regression] predcom-2 started to fail on arc-elf after r14-391 pinskia at gcc dot gnu.org 2023-05-03 22:20 ` pinskia at gcc dot gnu.org 2023-05-04 6:16 ` rguenth at gcc dot gnu.org 2023-05-04 8:06 ` rguenth at gcc dot gnu.org 2023-05-04 10:52 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-04 10:52 ` 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-109721-4-J3s9xZZ3xq@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).