From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V: Fix SEW64 of vrsub.vx runtime fail in RV32 system
Date: Tue, 4 Apr 2023 19:34:11 -0600 [thread overview]
Message-ID: <9a63e59f-d32d-3681-31d4-edb754147344@gmail.com> (raw)
In-Reply-To: <BA05F08C8A16F007+2023040312185834454250@rivai.ai>
On 4/2/23 22:18, juzhe.zhong@rivai.ai wrote:
> OK， would you mind telling me some tool can help for formatting of .MD
> file?
> Since clang-format only works on .cc/.h file.
No idea. I don't use clang-format. But I've also had 30+ years in this
codebase, so most of its coding conventions are ones that I've
internalized. When I do something outside GCC I struggle mightly to
conform to other conventions.
Given how often this construct seems to appear, perhaps move it into a
helper in the .cc file. That would seem to reduce code duplication and
allow you to use clang-format.
>
> I have asked many people how to format .MD file but I didn't get the answer.
> So that's why you can see formatting of .MD file is not good. Unlike
> .cc/.h files.
Can you force clang-format to treat it like C++ code?
jeff
next prev parent reply other threads:[~2023-04-05 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 0:38 juzhe.zhong
2023-04-03 4:13 ` Jeff Law
2023-04-03 4:18 ` juzhe.zhong
2023-04-05 1:34 ` Jeff Law [this message]
2023-04-05 13:49 ` 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=9a63e59f-d32d-3681-31d4-edb754147344@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).