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 middle-end/111125] [14 Regression] tree-ssa.exp and vect.exp failures after commit r14-3281-g99b5921bfc8f91 Date: Thu, 24 Aug 2023 08:15:32 +0000 [thread overview] Message-ID: <bug-111125-4-OqKVmAq46g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111125-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111125 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2023-08-24 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- For gcc.dg/tree-ssa/slsr-11.c we vectorize the reduction to <bb 2> [local count: 1073741824]: _15 = {s_5(D), s_5(D)}; vect_a3_11.3_16 = _15 * { 6, 4 }; vect__3.4_17 = (vector(2) long int) vect_a3_11.3_16; a1_6 = s_5(D) * 2; _18 = VIEW_CONVERT_EXPR<vector(2) unsigned long>(vect__3.4_17); _19 = .REDUC_PLUS (_18); _20 = (unsigned long) a1_6; _21 = (unsigned long) c_7(D); _29 = _21 * 2; _31 = _19 + _29; _30 = _20 + _21; _27 = _30 + _31; _28 = (long int) _27; return _28; note: Cost model analysis for part in loop 0: Vector cost: 9 Scalar cost: 9 doesn't look profitable. I think there's something off with the scalar accounting, I'll have a look there.
next prev parent reply other threads:[~2023-08-24 8:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-24 2:05 [Bug middle-end/111125] New: tree-ssa.exp and vect.exp failures after commit 99b5921bfc8f thiago.bauermann at linaro dot org 2023-08-24 7:41 ` [Bug middle-end/111125] [14 Regression] tree-ssa.exp and vect.exp failures after commit r14-3281-g99b5921bfc8f91 rguenth at gcc dot gnu.org 2023-08-24 8:15 ` rguenth at gcc dot gnu.org [this message] 2023-08-24 8:44 ` rguenth at gcc dot gnu.org 2023-08-24 8:54 ` rguenth at gcc dot gnu.org 2023-08-24 8:59 ` cvs-commit at gcc dot gnu.org 2023-08-24 9:36 ` cvs-commit at gcc dot gnu.org 2023-08-24 11:03 ` cvs-commit at gcc dot gnu.org 2023-08-24 11:03 ` rguenth at gcc dot gnu.org 2023-08-24 15:38 ` thiago.bauermann at linaro dot 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-111125-4-OqKVmAq46g@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).