From: Qing Zhao <qing.zhao@oracle.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH zero-call-used-regs] Add leafy mode for zero-call-used-regs
Date: Fri, 23 Jun 2023 14:47:11 +0000 [thread overview]
Message-ID: <ABE9382B-0211-480A-A544-2382D7B5E577@oracle.com> (raw)
In-Reply-To: <orpm5oqot2.fsf@lxoliva.fsfla.org>
Hi, Alexandre,
> On Jun 21, 2023, at 9:16 PM, Alexandre Oliva <oliva@adacore.com> wrote:
>
> Hello, Qing,
>
> On Jun 16, 2023, Qing Zhao <qing.zhao@oracle.com> wrote:
>
>> As I mentioned in the previous round of review, I think that the documentation
>> might need to add more details on what’s the LEAFY mode,
>> The purpose of it, and how to use it, provide more details to the end-users.
>
> I'm afraid I'm having difficulty picturing what it is that you're
> looking for. The proposal incorporates, by reference, all the
> documentation for 'used' and for 'all', and the way to use it is no
> different.
>
>>> +Same as @samp{used} in a leaf function, and same as @samp{all} in a
>>> +nonleaf function.
Oh, yeah. The definition of “leafy” is here. -:)
It’s better to add this definition earlier in the list of the “three basic values”, to make it “four basic values”, like the following:
=======
In order to satisfy users with different security needs and control the
run-time overhead at the same time, the @var{choice} parameter provides a
flexible way to choose the subset of the call-used registers to be zeroed.
The four basic values of @var{choice} are:
@itemize @bullet
@item
@samp{skip} doesn't zero any call-used registers.
@item
@samp{used} only zeros call-used registers that are used in the function.
A ``used'' register is one whose content has been set or referenced in
the function.
@item
@samp{all} zeros all call-used registers.
@end itemize
@item
@samp{leafy} Same as @samp{used} in a leaf function, and same as @samp{all} in a
nonleaf function. This value is mainly to provide users a more efficient mode to zero
call-used registers in leaf functions.
@end itemize
======
Then, in the full list of choice, add the new values of leafy, leafy-gpr, leafy-arg, leafy-gpr-arg
The sentence "This value is mainly to provide users a more efficient mode to zero
call-used registers in leaf functions.” just for your reference, the wording can certainly be improved. -:)
>
> If there was documentation on how to choose between e.g. all and used, I
> suppose I could build on that to add this intermediate choice, but... I
> can't find any such docs, and I'm uncertain on whether adding that would
> be useful to begin with.
>
> Did you have something else in mind?
Hope this time I am clear (and sorry for the confusion in the previous emails).
thanks.
Qing
>
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2023-06-23 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 7:31 Alexandre Oliva
2022-10-21 14:26 ` Qing Zhao
2022-10-25 2:48 ` Alexandre Oliva
2022-10-25 15:22 ` Qing Zhao
2022-10-26 21:29 ` Alexandre Oliva
2022-10-27 13:30 ` Qing Zhao
2023-06-16 7:26 ` Alexandre Oliva
2023-06-16 19:34 ` Qing Zhao
2023-06-22 1:16 ` Alexandre Oliva
2023-06-23 14:47 ` Qing Zhao [this message]
2023-06-23 23:27 ` [PATCH v3] " Alexandre Oliva
2023-06-26 13:58 ` Qing Zhao
2023-06-27 6:27 ` Richard Biener
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=ABE9382B-0211-480A-A544-2382D7B5E577@oracle.com \
--to=qing.zhao@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@adacore.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).