public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111006] [SVE] Extra neg for storing to short from int comparison Date: Sat, 12 Aug 2023 20:54:09 +0000 [thread overview] Message-ID: <bug-111006-4-DBBJqgXhlY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111006-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111006 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note the non-SVE code generation can be improved too. With: (simplify (negate (vec_pack_trunc:s (vec_cond:s @0 uniform_integer_cst_p@1 uniform_integer_cst_p@2) (vec_cond:s @3 @1 @2))) (with { tree outer_mask_type = truth_type_for (type); tree allones = build_minus_one_cst (type); tree zeros = build_zero_cst (type); } (if (integer_onep (@1) && integer_zerop (@2)) (vec_cond (vec_pack_trunc:outer_mask_type @0 @3) { allones; } { zeros; } ) (if (integer_onep (@2) && integer_zerop (@1)) (vec_cond (vec_pack_trunc:outer_mask_type @0 @3) { zeros; } { allones; } ))))) I will submit both later next week.
next prev parent reply other threads:[~2023-08-12 20:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-12 20:11 [Bug tree-optimization/111006] New: " pinskia at gcc dot gnu.org 2023-08-12 20:48 ` [Bug tree-optimization/111006] " pinskia at gcc dot gnu.org 2023-08-12 20:54 ` pinskia at gcc dot gnu.org [this message] 2023-08-15 22:03 ` pinskia at gcc dot gnu.org 2023-08-20 7:27 ` cvs-commit at gcc dot gnu.org 2023-08-20 7:27 ` pinskia 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-111006-4-DBBJqgXhlY@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).