public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Roger Sayle <roger@nextmovesoftware.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [ARC PATCH] Consistent use of whitespace in assembler templates.
Date: Tue, 21 Nov 2023 08:57:54 +0000	[thread overview]
Message-ID: <MW2PR12MB2346325389A6BB9E36DD4DFECABBA@MW2PR12MB2346.namprd12.prod.outlook.com> (raw)
In-Reply-To: <02c901da10e0$4537e260$cfa7a720$@nextmovesoftware.com>

Hi Roger,

Apologizes for late reply, I was in a short vacation. Please proceed with your commit. BTW, I consider this type of contribution as obvious, and you can always push it without waiting for my feedback.

Thank you for your contribution,
Claudiu

-----Original Message-----
From: Roger Sayle <roger@nextmovesoftware.com> 
Sent: Monday, November 6, 2023 8:37 PM
To: gcc-patches@gcc.gnu.org
Cc: 'Claudiu Zissulescu' <claziss@gmail.com>
Subject: [ARC PATCH] Consistent use of whitespace in assembler templates.


This minor clean-up patch tweaks arc.md to use whitespace consistently in output templates, always using a TAB between the mnemonic and its operands, and avoiding spaces after commas between operands.  There should be no functional changes with this patch, though several test cases' scan-assembler needed to be updated to use \s+ instead of testing for a TAB or a space explicitly.

Tested with a cross-compiler to arc-linux hosted on x86_64, with no new (compile-only) regressions from make -k check.
Ok for mainline if this passes Claudiu's nightly testing?


2023-11-06  Roger Sayle  <roger@nextmovesoftware.com>

gcc/ChangeLog
        * config/arc/arc.md: Make output template whitespace consistent.

gcc/testsuite/ChangeLog
        * gcc.target/arc/jli-1.c: Update dg-final whitespace.
        * gcc.target/arc/jli-2.c: Likewise.
        * gcc.target/arc/naked-1.c: Likewise.
        * gcc.target/arc/naked-2.c: Likewise.
        * gcc.target/arc/tmac-1.c: Likewise.
        * gcc.target/arc/tmac-2.c: Likewise.


Thanks again,
Roger
--


      reply	other threads:[~2023-11-21  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 18:37 Roger Sayle
2023-11-21  8:57 ` Claudiu Zissulescu [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=MW2PR12MB2346325389A6BB9E36DD4DFECABBA@MW2PR12MB2346.namprd12.prod.outlook.com \
    --to=claudiu.zissulescu@synopsys.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).