From: hilbert <swdtian@163.com>
To: joel@rtems.org
Cc: "Simon Marchi" <simark@simark.ca>,
"Eli Zaretskii via Gdb" <gdb@sourceware.org>
Subject: Re:Re: [question] If the code format is wrong, the _initialize_xxx functions cannot be generated?
Date: Tue, 31 Jan 2023 11:31:33 +0800 (CST) [thread overview]
Message-ID: <536cd874.31e2.18605e13f35.Coremail.swdtian@163.com> (raw)
In-Reply-To: <CAF9ehCUsQkjqzUxv3boSCOK4fJycN+CF6242dtehY0F1szHyqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Got it .
Thank you very much.
在 2023-01-31 10:10:27，"Joel Sherrill" <joel@rtems.org> 写道：
On Mon, Jan 30, 2023, 8:01 PM Simon Marchi via Gdb <gdb@sourceware.org> wrote:
On 1/30/23 20:58, hilbert via Gdb wrote:
> Sorry, it was my mistake.
>
> I downloaded a custom cudagdb project which has .clang-format file inside.
> So, which formatting tool do you need to use for the original GNU-GDB project?
There is none, we format the code by hand.
Many of us wish we could use a tool such as clang-format, but
unfortunately it's not configurable enough (despite its many
configuration options) to match our formatting and its many quirks.
FWIW RTEMS also has its own formatting quirks and clang-format appears to be within one option for us now. One of our core folks was considering addressing that one.
They get better and better so worth looking periodically.
--joel
Simon
next prev parent reply other threads:[~2023-01-31 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:15 hilbert
2023-01-30 3:03 ` Simon Marchi
2023-01-30 8:30 ` hilbert
2023-01-31 1:28 ` Simon Marchi
2023-01-31 1:58 ` hilbert
2023-01-31 2:01 ` Simon Marchi
2023-01-31 2:10 ` Joel Sherrill
2023-01-31 3:31 ` hilbert [this message]
2023-02-08 19:58 ` Tom Tromey
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=536cd874.31e2.18605e13f35.Coremail.swdtian@163.com \
--to=swdtian@163.com \
--cc=gdb@sourceware.org \
--cc=joel@rtems.org \
--cc=simark@simark.ca \
/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).