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/64154] enable fipa-ra for Thumb1 Date: Mon, 10 Jan 2022 00:21:10 +0000 [thread overview] Message-ID: <bug-64154-4-WmqCEKV0p7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64154-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64154 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |FIXME Last reconfirmed|2014-12-12 00:00:00 |2022-1-9 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note the code is now: /* In Thumb1 mode, we emit the epilogue in RTL, but the last insn - epilogue_insns - does not accurately model the corresponding insns emitted in the asm file. In particular, see the comment in thumb_exit 'Find out how many of the (return) argument registers we can corrupt'. As a consequence, the epilogue may clobber registers without fipa-ra finding out about it. Therefore, disable fipa-ra in Thumb1 mode. TODO: Accurately model clobbers for epilogue_insns and reenable fipa-ra. */ if (TARGET_THUMB1_P (opts->x_target_flags)) opts->x_flag_ipa_ra = 0; else opts->x_flag_ipa_ra = to->x_flag_ipa_ra;
prev parent reply other threads:[~2022-01-10 0:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-02 17:17 [Bug target/64154] New: enable fuse-caller-save " vries at gcc dot gnu.org 2014-12-03 10:34 ` [Bug target/64154] enable fipa-ra " vries at gcc dot gnu.org 2014-12-12 14:59 ` ramana at gcc dot gnu.org 2015-01-08 8:17 ` terry.guo at arm dot com 2015-01-08 13:55 ` vries at gcc dot gnu.org 2015-01-08 14:18 ` vries at gcc dot gnu.org 2022-01-10 0:21 ` 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-64154-4-WmqCEKV0p7@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: linkBe 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).