public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Tamar Christina via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, Richard Sandiford <Richard.Sandiford@arm.com>,
	Tamar Christina <Tamar.Christina@arm.com>
Subject: Re: [PATCH v2] machine descriptor: New compact syntax for insn and insn_split in Machine Descriptions.
Date: Thu, 8 Jun 2023 11:33:11 +0100	[thread overview]
Message-ID: <df1c066a-e735-1a87-47da-0bc3a25b255e@arm.com> (raw)
In-Reply-To: <ad4bfc89-3c61-3857-d232-4875df151d8d@arm.com>

On 08/06/2023 11:29, Richard Earnshaw (lists) via Gcc-patches wrote:
> On 08/06/2023 11:12, Andreas Schwab wrote:
>> On Jun 08 2023, Tamar Christina via Gcc-patches wrote:
>>
>>> @@ -713,6 +714,183 @@ you can use @samp{*} inside of a @samp{@@} 
>>> multi-alternative template:
>>>   @end group
>>>   @end smallexample
>>> +@node Compact Syntax
>>> +@section Compact Syntax
>>> +@cindex compact syntax
>>> +
>>> +In cases where the number of alternatives in a @code{define_insn} or
>>> +@code{define_insn_and_split} are large then it may be beneficial to 
>>> use the
>>
>>                                  is large
>>
> 
> Or perhaps better still:
> 
> When a define_insn or define_insn_and split has many alternatives it may 
> be beneficial to ...
> 
> R.

Or perhaps even s/many/multiple/.  It doesn't have to have very many to 
make this new syntax preferable, IMO.

R.

  reply	other threads:[~2023-06-08 10:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 16:30 [PATCH] RFC: " Tamar Christina
2023-04-21 17:18 ` Richard Sandiford
2023-04-24  8:33   ` Richard Sandiford
2023-05-16 13:56     ` Richard Earnshaw (lists)
2023-04-24  9:05   ` Tamar Christina
2023-04-24  9:37     ` Richard Sandiford
2023-06-05 13:51 ` [PATCH v2] machine descriptor: " Tamar Christina
2023-06-05 20:35 ` Richard Sandiford
2023-06-06  7:47   ` Richard Sandiford
2023-06-06 12:00   ` Tamar Christina
2023-06-06 12:49     ` Richard Sandiford
2023-06-06 16:13       ` Richard Earnshaw (lists)
2023-06-08  9:58         ` Tamar Christina
2023-06-08 10:12           ` Andreas Schwab
2023-06-08 10:29             ` Richard Earnshaw (lists)
2023-06-08 10:33               ` Richard Earnshaw (lists) [this message]
2023-06-08 14:24           ` Richard Sandiford
2023-06-08 16:49           ` Mikael Morin
2023-06-13 15:26             ` Tamar Christina
2023-06-14 19:41               ` Richard Sandiford
2023-06-15  6:24                 ` Richard Sandiford

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=df1c066a-e735-1a87-47da-0bc3a25b255e@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=Tamar.Christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=schwab@linux-m68k.org \
    /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).