public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115382] New: Wrong code with in-order conditional reduction and masked loops Date: Fri, 07 Jun 2024 08:17:55 +0000 [thread overview] Message-ID: <bug-115382-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115382 Bug ID: 115382 Summary: Wrong code with in-order conditional reduction and masked loops Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- vectorize_fold_left_reduction does if (LOOP_VINFO_FULLY_MASKED_P (loop_vinfo)) mask = vect_get_loop_mask (loop_vinfo, gsi, masks, vec_num, vectype_in, i); else if (is_cond_op) mask = vec_opmask[i]; that doesn't work - both masks have to be combined. This for example shows in a runfail of gcc.dg/vect/vect-cond-reduc-in-order-2-signed-zero.c with -march=cascadelake --param vect-partial-vector-usage=2 on x86_64. The len-masking code looks good.
next reply other threads:[~2024-06-07 8:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-07 8:17 rguenth at gcc dot gnu.org [this message] 2024-06-07 19:02 ` [Bug tree-optimization/115382] " rdapp at gcc dot gnu.org 2024-06-10 6:18 ` rguenth at gcc dot gnu.org 2024-06-10 6:49 ` rdapp at gcc dot gnu.org 2024-06-10 7:12 ` rguenth at gcc dot gnu.org 2024-06-11 18:10 ` cvs-commit at gcc dot gnu.org 2024-06-12 7:03 ` rguenth at gcc dot gnu.org 2024-06-12 7:33 ` rdapp 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-115382-4@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).