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 rtl-optimization/95405] Unnecessary stores with std::optional
Date: Sun, 07 Mar 2021 07:32:53 +0000 [thread overview]
Message-ID: <bug-95405-4-jAln7nwWLa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95405-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95405
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Ever confirmed|0 |1
Last reconfirmed| |2021-03-07
Component|tree-optimization |rtl-optimization
Target| |x86_64-linux-gnu
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
On aarch64 we do the correct thing:
_Z3barv:
stp x29, x30, [sp, -32]!
mov x29, sp
bl _Z3foov
tst w1, 255
csel x0, x0, xzr, ne
ldp x29, x30, [sp], 32
ret
So this is most likely an issue with how x86_64 implements stuff.
Confirmed for x86_64 though.
next prev parent reply other threads:[~2021-03-07 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:38 [Bug c++/95405] New: " steffen.hirschmann at ipvs dot uni-stuttgart.de
2021-03-07 7:32 ` pinskia at gcc dot gnu.org [this message]
2021-06-06 15:30 ` [Bug rtl-optimization/95405] " gabravier at gmail dot com
2021-06-06 18:07 ` glisse at gcc dot gnu.org
2021-06-06 18:11 ` gabravier at gmail dot com
2021-06-06 18:58 ` glisse at gcc dot gnu.org
2023-07-12 21:34 ` pinskia at gcc dot gnu.org
2023-07-12 21:35 ` pinskia at gcc dot gnu.org
2023-07-12 21:35 ` pinskia at gcc dot gnu.org
2023-07-12 21:35 ` pinskia 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-95405-4-jAln7nwWLa@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).