From: Alexandre Oliva <oliva@adacore.com>
To: Qing Zhao <qing.zhao@oracle.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: Wed, 21 Jun 2023 22:16:25 -0300 [thread overview]
Message-ID: <orpm5oqot2.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <80999785-4FFD-4C6E-B501-57E92F45053A@oracle.com> (Qing Zhao's message of "Fri, 16 Jun 2023 19:34:25 +0000")
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.
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?
--
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-22 1:16 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 [this message]
2023-06-23 14:47 ` Qing Zhao
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=orpm5oqot2.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=qing.zhao@oracle.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).