From: Richard Sandiford <richard.sandiford@arm.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Jeff Law <jlaw@ventanamicro.com>,
"gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA] [V3] new pass for sign/zero extension elimination
Date: Mon, 08 Jan 2024 15:45:10 +0000 [thread overview]
Message-ID: <mptplybzv5l.fsf@arm.com> (raw)
In-Reply-To: <9782d6d2-591c-47eb-9e41-49b06a7c1bf2@gmail.com> (Jeff Law's message of "Sun, 7 Jan 2024 16:30:24 -0700")
Jeff Law <jeffreyalaw@gmail.com> writes:
>>> +
>>> +/* Initialization of the ext-dce pass. Primarily this means
>>> + setting up the various bitmaps we utilize. */
>>> +
>>> +static void
>>> +ext_dce_init (void)
>>> +{
>>> +
>>
>> Nit: excess blank line.
> Various nits have been fixed. I think those are all mine. For reasons
> I don't understand to this day, my brain thinks there should be vertical
> whitespace between the function comment and the definition. I'm
> constantly having to fix that.
Yeah, I've never known whether a blank line is preferred between the
comment and function definition. When I started (obviously somewhat
later than you :)), "yes" seemed to be much more common, but now it's
pretty mixed. So I just do what surrounding code does. (Personally
I slightly prefer the blank line.)
So I wasn't commenting on that part, although reading it back, I can
see how it looked like that. It was just on the blank line immediately
above, after the opening "{". I.e. there were some instances of:
void
f (void)
{
...foo...;
}
rather than:
void
f (void)
{
...foo...;
}
Thanks,
Richard
next prev parent reply other threads:[~2024-01-08 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 21:04 Jeff Law
2024-01-03 12:07 ` Richard Sandiford
2024-01-03 16:54 ` Richard Sandiford
2024-01-07 23:30 ` Jeff Law
2024-01-08 15:45 ` Richard Sandiford [this message]
2024-01-16 15:24 ` Jeff Law
2024-01-04 13:36 ` Stefan Schulze Frielinghaus
2024-01-04 20:07 ` Jeff Law
2024-01-04 20:44 ` Xi Ruoyao
2024-01-05 16:06 ` 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=mptplybzv5l.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.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).