From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org, jlaw@ventanamicro.com,
richard.sandiford@arm.com
Subject: Re: [PATCH 01/12] mode-switching: Tweak the macro/hook documentation
Date: Mon, 6 Nov 2023 17:10:23 -0700 [thread overview]
Message-ID: <889a8f0c-c22f-40d4-8bdc-a90b0017840f@gmail.com> (raw)
In-Reply-To: <mptwmuw82dh.fsf@arm.com>
On 11/5/23 11:46, Richard Sandiford wrote:
> I found the documentation for the mode-switching macros/hooks
> a bit hard to follow at first. This patch tries to add the
> information that I think would have made it easier to understand.
>
> Of course, documentation preferences are personal, and so I could
> be changing something that others understood to something that
> seems impenetrable.
>
> Some notes on specific changes:
>
> - "in an optimizing compilation" didn't seem accurate; the pass
> is run even at -O0, and often needs to be for correctness.
>
> - "at run time" meant when the compiler was run, rather than when
> the compiled code was run.
>
> - Removing the list of optional macros isn't a clarification,
> but it means that upcoming patches don't create an absurdly
> long list.
>
> - I don't really understand the purpose of TARGET_MODE_PRIORITY,
> so I mostly left that alone.
>
> gcc/
> * target.def: Tweak documentation of mode-switching hooks.
> * doc/tm.texi.in (OPTIMIZE_MODE_SWITCHING): Tweak documentation.
> (NUM_MODES_FOR_MODE_SWITCHING): Likewise.
> * doc/tm.texi: Regenerate.
OK. I doubt very many people have looked at this stuff. I think the
only targets implementing mode switching are x86, sh and riscv, and soon
aarch64 and for the most part I think most folks try to ignore it ;-)
jeff
next prev parent reply other threads:[~2023-11-07 0:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 18:45 [PATCH 00/12] Tweaks and extensions to the mode-switching pass Richard Sandiford
2023-11-05 18:46 ` [PATCH 01/12] mode-switching: Tweak the macro/hook documentation Richard Sandiford
2023-11-07 0:10 ` Jeff Law [this message]
2023-11-05 18:46 ` [PATCH 02/12] mode-switching: Add note problem Richard Sandiford
2023-11-07 0:11 ` Jeff Law
2023-11-05 18:47 ` [PATCH 03/12] mode-switching: Avoid quadractic list operation Richard Sandiford
2023-11-07 0:47 ` Jeff Law
2023-11-05 18:47 ` [PATCH 04/12] mode-switching: Fix the mode passed to the emit hook Richard Sandiford
2023-11-07 0:51 ` Jeff Law
2023-11-05 18:47 ` [PATCH 05/12] mode-switching: Simplify recording of transparency Richard Sandiford
2023-11-07 0:52 ` Jeff Law
2023-11-05 18:48 ` [PATCH 06/12] mode-switching: Tweak entry/exit handling Richard Sandiford
2023-11-07 1:01 ` Jeff Law
2023-11-05 18:48 ` [PATCH 07/12] mode-switching: Allow targets to set the mode for EH handlers Richard Sandiford
2023-11-07 1:07 ` Jeff Law
2023-11-08 0:15 ` Richard Sandiford
2023-11-08 2:24 ` Jeff Law
2023-11-05 18:48 ` [PATCH 08/12] mode-switching: Pass set of live registers to the needed hook Richard Sandiford
2023-11-07 1:11 ` Jeff Law
2023-11-05 18:49 ` [PATCH 09/12] mode-switching: Pass the set of live registers to the after hook Richard Sandiford
2023-11-07 1:12 ` Jeff Law
2023-11-05 18:49 ` [PATCH 10/12] mode-switching: Use 1-based edge aux fields Richard Sandiford
2023-11-07 2:53 ` Jeff Law
2023-11-08 0:35 ` Richard Sandiford
2023-11-08 2:22 ` Jeff Law
2023-11-11 15:51 ` Richard Sandiford
2023-11-11 16:19 ` Jeff Law
2023-11-05 18:50 ` [PATCH 11/12] mode-switching: Add a target-configurable confluence operator Richard Sandiford
2023-11-07 3:04 ` Jeff Law
2023-11-11 15:54 ` Richard Sandiford
2023-11-11 16:19 ` Jeff Law
2023-11-11 17:29 ` Richard Sandiford
2023-11-05 18:50 ` [PATCH 12/12] mode-switching: Add a backprop hook Richard Sandiford
2023-11-10 1:18 ` Jeff Law
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=889a8f0c-c22f-40d4-8bdc-a90b0017840f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=richard.sandiford@arm.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).