From: Mikael Morin <morin-mikael@orange.fr>
To: Tamar Christina <Tamar.Christina@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
nd <nd@arm.com>, Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: [PATCH v2] machine descriptor: New compact syntax for insn and insn_split in Machine Descriptions.
Date: Thu, 8 Jun 2023 18:49:02 +0200 [thread overview]
Message-ID: <30f06911-e19a-a39b-9b56-803cc9ef0ec1@orange.fr> (raw)
In-Reply-To: <VI1PR08MB532500C80282451D7D8524D0FF50A@VI1PR08MB5325.eurprd08.prod.outlook.com>
Le 08/06/2023 à 11:58, Tamar Christina via Gcc-patches a écrit :
> Hi,
>
> New version of the patch, I've omitted the explanation again 😊
>
> Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
>
> Any feedback?
>
Hello,
this is not my area of expertise, but I saw the following:
> + /* [ns..ns + len) should be a string with the id of the rtx to match
> + i.e. if rtx is the relevant match_operand or match_scratch then
> + [ns..ns + len) should equal itoa (XINT (rtx, 0)), and if set_attr then
> + [ns..ns + len) should equal XSTR (rtx, 0). */
> + conlist (const char *ns, unsigned int len, bool numeric)
> + {
> + /* Trim leading whitespaces. */
> + while (ISSPACE (*ns))
> + {
> + ns++;
> + len--;
> + }
> +
> + /* Trim trailing whitespace. */
> + for (int i = len - 1; i >= 0; i++, len--)
> + if (!ISSPACE (*ns))
> + break;
> +
This for loop makes little sense to me. Shouldn't the iteration step be
i-- rather than i++ and the pointer dereference *(ns + i) rather than *ns?
next prev parent reply other threads:[~2023-06-08 16:49 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)
2023-06-08 14:24 ` Richard Sandiford
2023-06-08 16:49 ` Mikael Morin [this message]
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=30f06911-e19a-a39b-9b56-803cc9ef0ec1@orange.fr \
--to=morin-mikael@orange.fr \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=Tamar.Christina@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).