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/104438] Combine optimization opportunity exposed after pro_and_epilogue
Date: Wed, 09 Feb 2022 04:17:25 +0000 [thread overview]
Message-ID: <bug-104438-4-aNPuaxJH5E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104438-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104438
--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #4)
> > It is unclear why the CFG wasn't straightened out here. Is the bb commented
> > as "asm" actually asm? Then GCC will not see it is very cheap/small, yeah.
>
> "asm" is not inline assembly. it's BB 6 below
>
> (note 89 88 126 6 [bb 6] NOTE_INSN_BASIC_BLOCK)
> (call_insn 126 89 121 6 (parallel [
> (call (mem:QI (const_int 0 [0]) [0 S1 A8])
> (const_int 0 [0]))
> (unspec [
> (const_int 1 [0x1])
> ] UNSPEC_CALLEE_ABI)
> ]) -1
> (expr_list:REG_EH_REGION (const_int -2147483648 [0xffffffff80000000])
> (nil))
> (nil))
According to PR104441, vzeroupper shouldn't be inserted here, after fix of
PR104441, CFG wasn't straightened.
next prev parent reply other threads:[~2022-02-09 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 4:29 [Bug target/104438] New: Combine optimization " crazylht at gmail dot com
2022-02-08 9:15 ` [Bug rtl-optimization/104438] Combine optimization opportunity " rguenth at gcc dot gnu.org
2022-02-08 9:50 ` rsandifo at gcc dot gnu.org
2022-02-08 14:42 ` segher at gcc dot gnu.org
2022-02-09 2:41 ` crazylht at gmail dot com
2022-02-09 4:17 ` crazylht at gmail dot com [this message]
2022-02-10 3:00 ` crazylht at gmail dot com
2022-02-10 3:01 ` crazylht at gmail dot com
2022-02-24 10:46 ` marxin at gcc dot gnu.org
2022-02-25 1:06 ` 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-104438-4-aNPuaxJH5E@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).