From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, wschmidt@linux.ibm.com
Subject: Re: [PATCH, rs6000]: mark clobber for registers changed by untpyed_call
Date: Sat, 08 Feb 2020 21:45:00 -0000 [thread overview]
Message-ID: <20200208214514.GE22482@gate.crashing.org> (raw)
In-Reply-To: <20200208161742.GY22482@gate.crashing.org>
On Sat, Feb 08, 2020 at 10:17:42AM -0600, Segher Boessenkool wrote:
> And we do not know which of the register will be used for the return, in
> untyped_call (only untyped-return knows). But we can add clobbers of all
> registers that *might* be used for the return, we do know that here, see
> operands[2] of untyped_call.
Clobbers in parallel to the call, I mean, not as separate insns later.
Segher
next prev parent reply other threads:[~2020-02-08 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 13:53 Jiufu Guo
2020-02-05 19:25 ` Segher Boessenkool
2020-02-06 2:49 ` Jiufu Guo
2020-02-06 15:35 ` Segher Boessenkool
2020-02-07 7:10 ` Jiufu Guo
2020-02-08 16:17 ` Segher Boessenkool
2020-02-08 21:45 ` Segher Boessenkool [this message]
2020-02-14 6:58 ` Jiufu Guo
2020-02-14 18:12 ` Segher Boessenkool
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=20200208214514.GE22482@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=wschmidt@linux.ibm.com \
/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).