public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mxlol233 at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/111558] RISCV: shrink-wrapper optimization question
Date: Tue, 26 Sep 2023 13:26:30 +0000 [thread overview]
Message-ID: <bug-111558-4-1quFzGhnyn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111558-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111558
--- Comment #3 from Xiao Ma <mxlol233 at outlook dot com> ---
(In reply to Xiao Ma from comment #2)
> For this piece of code, LLVM seems to be a bit concise: during the pass of
> Prologue/Epilogue Insertion & Frame Finalization, it only inserts sd/ld
> blocks in the entry and exit BB:
>
> https://godbolt.org/z/qxdrMKc46
On the contrary, GCC emits sd/ld blocks for each of BB, in the pro_and_epilogue
pass:
https://godbolt.org/z/vY4M71snz
prev parent reply other threads:[~2023-09-26 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 21:00 [Bug c/111558] New: " alexey.lapshin at espressif dot com
2023-09-23 21:17 ` [Bug rtl-optimization/111558] " pinskia at gcc dot gnu.org
2023-09-26 13:19 ` mxlol233 at outlook dot com
2023-09-26 13:26 ` mxlol233 at outlook dot com [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-111558-4-1quFzGhnyn@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).