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/108752] word_mode vectorization is pessimized by hard limit on nunits Date: Tue, 23 May 2023 16:10:13 +0000 [thread overview] Message-ID: <bug-108752-4-TigM67wlSw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108752-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108752 --- Comment #6 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:9d5034aad9868bed45472ef5bfac22dd9ac0e0cb commit r14-1136-g9d5034aad9868bed45472ef5bfac22dd9ac0e0cb Author: Richard Biener <rguenther@suse.de> Date: Tue May 23 15:58:52 2023 +0200 Generic vector op costing adjustment This is a small adjustment to the work done for PR108752 and better reflects the cost of the generated sequence. PR tree-optimization/108752 * tree-vect-stmts.cc (vectorizable_operation): For bit operations with generic word_mode vectors do not cost an extra stmt. For plus, minus and negate also cost the constant materialization.
prev parent reply other threads:[~2023-05-23 16:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-10 11:24 [Bug tree-optimization/108752] New: " rguenth at gcc dot gnu.org 2023-02-10 11:24 ` [Bug tree-optimization/108752] " rguenth at gcc dot gnu.org 2023-02-10 12:12 ` rguenth at gcc dot gnu.org 2023-02-12 23:49 ` hp at gcc dot gnu.org 2023-04-28 9:07 ` cvs-commit at gcc dot gnu.org 2023-04-28 9:08 ` rguenth at gcc dot gnu.org 2023-05-23 16:10 ` 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-108752-4-TigM67wlSw@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).