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 target/82730] extra store/reload of an XMM for every byte extracted
Date: Sun, 15 Aug 2021 10:51:16 +0000 [thread overview]
Message-ID: <bug-82730-4-j52QYxdxGk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82730-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82730
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Severity|normal |enhancement
Ever confirmed|0 |1
Last reconfirmed| |2021-08-15
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note the gimple level looks good:
_20 = BIT_FIELD_REF <in_18(D), 8, 120>;
_1 = (int) _20;
_21 = BIT_FIELD_REF <in_18(D), 8, 112>;
_2 = (int) _21;
_22 = BIT_FIELD_REF <in_18(D), 8, 104>;
_3 = (int) _22;
_23 = BIT_FIELD_REF <in_18(D), 8, 96>;
_4 = (int) _23;
_24 = BIT_FIELD_REF <in_18(D), 8, 88>;
_5 = (int) _24;
_25 = BIT_FIELD_REF <in_18(D), 8, 80>;
_6 = (int) _25;
_26 = BIT_FIELD_REF <in_18(D), 8, 72>;
_7 = (int) _26;
_27 = BIT_FIELD_REF <in_18(D), 8, 64>;
_8 = (int) _27;
_28 = BIT_FIELD_REF <in_18(D), 8, 56>;
_9 = (int) _28;
_29 = BIT_FIELD_REF <in_18(D), 8, 48>;
_10 = (int) _29;
_30 = BIT_FIELD_REF <in_18(D), 8, 40>;
_11 = (int) _30;
_31 = BIT_FIELD_REF <in_18(D), 8, 32>;
_12 = (int) _31;
_32 = BIT_FIELD_REF <in_18(D), 8, 24>;
_13 = (int) _32;
_33 = BIT_FIELD_REF <in_18(D), 8, 16>;
_14 = (int) _33;
_34 = BIT_FIELD_REF <in_18(D), 8, 8>;
_15 = (int) _34;
_35 = BIT_FIELD_REF <in_18(D), 8, 0>;
_16 = (int) _35;
----- CUT ----
It is the way extractions are done for bytes is not good.
Note MSVC is the only one which does extractions in a register only and not do
a store to the stack.
next parent reply other threads:[~2021-08-15 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82730-4@http.gcc.gnu.org/bugzilla/>
2021-08-15 10:51 ` pinskia at gcc dot gnu.org [this message]
2021-08-19 6:25 ` 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-82730-4-j52QYxdxGk@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).