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/64322] More optimize opportunity for constant folding
Date: Thu, 19 Aug 2021 19:26:26 +0000 [thread overview]
Message-ID: <bug-64322-4-Bs1IWg3CD0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64322-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64322
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Target Milestone|--- |5.0
Status|NEW |RESOLVED
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #10)
> (In reply to Martin Liška from comment #9)
> > Can the bug be marked as resolved?
>
> Did you check? At -Os we now produce for A
>
> movq $0, -16(%rsp)
> movl $1, %eax
> salq $32, %rax
> movq %rax, -8(%rsp)
> movq -16(%rsp), %rax
> xorl %eax, %eax
> ret
movabs $0x100000000,%rax
is 10 bytes while
mov $0x1,%eax
shl $0x20,%rax
is also 9 bytes.
Counting instructions on x86_64 with -Os is not always the best thing to do :).
Yes it is fixed and even improved.
prev parent reply other threads:[~2021-08-19 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:01 [Bug tree-optimization/64322] New: " ishiura-compiler at ml dot kwansei.ac.jp
2014-12-16 0:41 ` [Bug tree-optimization/64322] " jakub at gcc dot gnu.org
2014-12-16 10:11 ` rguenth at gcc dot gnu.org
2014-12-16 10:26 ` jakub at gcc dot gnu.org
2014-12-16 11:50 ` rguenth at gcc dot gnu.org
2014-12-17 9:29 ` jakub at gcc dot gnu.org
2014-12-17 12:36 ` jakub at gcc dot gnu.org
2014-12-17 14:25 ` rguenther at suse dot de
2021-08-19 19:26 ` pinskia at gcc dot gnu.org [this message]
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-64322-4-Bs1IWg3CD0@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).