public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112361] [14 Regression] avx512f-reduce-op-1.c miscompiled since r14-5076 Date: Mon, 06 Nov 2023 09:51:54 +0000 [thread overview] Message-ID: <bug-112361-4-4zOyB4DDdt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112361 --- Comment #6 from Robin Dapp <rdapp at gcc dot gnu.org> --- So "before" we created vect__3.12_55 = MEM <vector(16) float> [(float *)vectp_a.10_53]; vect__ifc__43.13_57 = VEC_COND_EXPR <mask__24.9_52, vect__3.12_55, { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0 }>; // _ifc__43 = _24 ? _3 : 0.0; stmp__44.14_58 = BIT_FIELD_REF <vect__ifc__43.13_57, 32, 0>; stmp__44.14_59 = r3_29 + stmp__44.14_58; ... in vect_expand_fold_left. Now, as intended, there is no VEC_COND anymore and we just create the bit-field reduction over the unmasked vector. We could refrain from creating the COND_OP in the first place as Jakub mentioned (I guess we know already in if-conv that we shouldn't), re-insert a VEC_COND or create a COND_OP chain (instead of an OP chain) in vect_expand_fold_left by passing it the mask (and is_cond_op). Having several COND_OPs here might make analysis of subsequent passes more difficult?
next prev parent reply other threads:[~2023-11-06 9:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-03 7:20 [Bug tree-optimization/112361] New: " jakub at gcc dot gnu.org 2023-11-03 7:20 ` [Bug tree-optimization/112361] " jakub at gcc dot gnu.org 2023-11-03 7:22 ` pinskia at gcc dot gnu.org 2023-11-03 7:51 ` rdapp at gcc dot gnu.org 2023-11-03 8:13 ` rguenth at gcc dot gnu.org 2023-11-03 8:14 ` jakub at gcc dot gnu.org 2023-11-04 5:24 ` pinskia at gcc dot gnu.org 2023-11-06 9:51 ` rdapp at gcc dot gnu.org [this message] 2023-11-06 10:06 ` rguenther at suse dot de 2023-11-07 21:38 ` cvs-commit at gcc dot gnu.org 2023-11-08 7:01 ` 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-112361-4-4zOyB4DDdt@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).