public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/107775] New: misoptimization in vec_set lower part of vector in the memory.
Date: Mon, 21 Nov 2022 02:43:29 +0000	[thread overview]
Message-ID: <bug-107775-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107775

            Bug ID: 107775
           Summary: misoptimization in vec_set lower part of vector in the
                    memory.
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: crazylht at gmail dot com
                CC: tnfchris at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64-linux-gnu

The case is found when i'm looking at
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606373.html, currently
x86 gcc can optimize set_lower same as set_lower1, but not after adjusting in
can_change_mode_class. The issue can be reproduce with aarch64 gcc. I'm looking
at rtl dump, the main difference comes from subreg1, where currently it will
split 128-bit load/store into 2 64-bit load/stores which expose the opportunity
to optimize the upper 64-bit load/store off.

typedef double v2df __attribute__((vector_size(16)));

v2df reg;
void
set_lower (double b)
{
  double v[2];
  *((v2df*)&v[0]) = reg;
  v[0] = b;
  reg = *((v2df*)&v[0]);
}


void
set_lower1 (double b)
{
    reg[0] = b;
}

             reply	other threads:[~2022-11-21  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21  2:43 crazylht at gmail dot com [this message]
2022-11-22  8:34 ` [Bug rtl-optimization/107775] " rguenth at gcc dot gnu.org
2022-11-22  8:45 ` crazylht at gmail dot com

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-107775-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: link
Be 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).