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/102575] Failure to optimize double _Complex stores to use largest loads/stores possible Date: Sun, 03 Oct 2021 18:48:59 +0000 [thread overview] Message-ID: <bug-102575-4-cYx2N3ur7d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102575-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102575 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |tree-optimization Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2021-10-03 Severity|normal |enhancement --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /app/example.cpp:5:1: note: === vect_slp_analyze_bb === /app/example.cpp:5:1: note: === vect_analyze_data_refs === /app/example.cpp:5:1: missed: not vectorized: no vectype for stmt: *a_2(D) = __complex__ (1.0e+0, 0.0); scalar_type: complex double /app/example.cpp:5:1: missed: not vectorized: no vectype for stmt: MEM[(complex double *)a_2(D) + 16B] = __complex__ (1.0e+0, 0.0); scalar_type: complex double /app/example.cpp:5:1: note: === vect_analyze_data_ref_accesses === /app/example.cpp:5:1: missed: not vectorized: no grouped stores in basic block. /app/example.cpp:5:1: note: ***** Analysis failed with vector mode VOID void test (complex double * a) Yes SLP does not understand how to handle complex double And then expand splits the complex type store into two different stores.
next prev parent reply other threads:[~2021-10-03 18:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-03 14:01 [Bug target/102575] New: " gabravier at gmail dot com 2021-10-03 18:48 ` pinskia at gcc dot gnu.org [this message] 2021-10-04 7:21 ` [Bug tree-optimization/102575] " rguenth at gcc dot gnu.org 2022-07-20 8:18 ` crazylht at gmail dot com 2022-07-20 9:06 ` 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-102575-4-cYx2N3ur7d@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).