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/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking Date: Thu, 29 Jun 2023 09:57:17 +0000 [thread overview] Message-ID: <bug-110460-4-AjBtgsDKg3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110460-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 --- 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:cd23ed2119120bd7b710fbe679fdfcb8f4461800 commit r14-2186-gcd23ed2119120bd7b710fbe679fdfcb8f4461800 Author: Richard Biener <rguenther@suse.de> Date: Thu Jun 29 10:23:29 2023 +0200 tree-optimization/110460 - fend off vector types from vectorizer The following makes fending off existing vector types from vectorization also apply to word_mode vector types. I've chosen to add a positive list of allowed scalar types here for clarity. PR tree-optimization/110460 * tree-vect-stmts.cc (get_related_vectype_for_scalar_type): Only allow integral, pointer and scalar float type scalar_type.
next prev parent reply other threads:[~2023-06-29 9:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 15:34 [Bug tree-optimization/110460] New: " law at gcc dot gnu.org 2023-06-28 19:34 ` [Bug tree-optimization/110460] " pinskia at gcc dot gnu.org 2023-06-29 7:35 ` rguenth at gcc dot gnu.org 2023-06-29 7:38 ` rguenth at gcc dot gnu.org 2023-06-29 8:42 ` ro at gcc dot gnu.org 2023-06-29 9:57 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-29 9:59 ` rguenth at gcc dot gnu.org 2023-06-29 10:33 ` manuel.lauss at googlemail dot com
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-110460-4-AjBtgsDKg3@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).