From: Sandra Loosemore <sandra@codesourcery.com>
To: Roger Sayle <roger@nextmovesoftware.com>,
'GCC Patches' <gcc-patches@gcc.gnu.org>
Subject: Re: [DOC PATCH] Document the VEC_PERM_EXPR tree code (and minor clean-ups).
Date: Sat, 11 Mar 2023 18:37:02 -0700 [thread overview]
Message-ID: <81c02a97-bfca-08bd-b23b-d4f28c99824a@codesourcery.com> (raw)
In-Reply-To: <000f01d938d8$00cdf7d0$0269e770$@nextmovesoftware.com>
On 2/4/23 13:33, Roger Sayle wrote:
>
> This patch (primarily) documents the VEC_PERM_EXPR tree code in
> generic.texi. For ease of review, it is provided below as a pair
> of diffs. The first contains just the new text added to describe
> VEC_PERM_EXPR, the second tidies up this part of the documentation
> by sorting the tree codes into alphabetical order, and providing
> consistent section naming/capitalization, so changing this section
> from "Vectors" to "Vector Expressions" (matching the nearby
> "Unary and Binary Expressions").
>
> Tested with make pdf and make html on x86_64-pc-linux-gnu.
> The reviewer(s) can decide whether to approve just the new content,
> or the content+clean-up. Ok for mainline?
>
>
> 2023-02-04 Roger Sayle <roger@nextmovesoftware.com>
>
> gcc/ChangeLog
> * doc/generic.texi <Expression Trees>: Standardize capitalization
> of section titles from "Expression trees".
> <Language-dependent Trees>: Likewise standardize capitalization
> from "Language-dependent trees".
> <Constant expressions>: Capitalized from "Constant Expressions".
> <Vector Expressions>: Standardized section name from "Vectors".
> Document VEC_PERM_EXPR tree code. Sort tree codes alphabetically.
Trying to catch up on old mail here....
IIUC the proposed VEC_PERM_EXPR wording was rejected on technical
grounds. I confess I know nothing about this, so I can't usefully
suggest alternate wording myself. :-(
The other changes look OK except that the correct capitalization would
be "Language-Dependent Trees".
-Sandra
prev parent reply other threads:[~2023-03-12 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 20:33 Roger Sayle
2023-02-06 7:10 ` Richard Biener
2023-02-06 12:22 ` Richard Sandiford
2023-02-06 14:44 ` Roger Sayle
2023-02-07 8:07 ` Prathamesh Kulkarni
2023-03-12 1:37 ` Sandra Loosemore [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=81c02a97-bfca-08bd-b23b-d4f28c99824a@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.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).