From: Joel Sherrill <joel@rtems.org>
To: Simon Marchi <simark@simark.ca>
Cc: hilbert <swdtian@163.com>, Eli Zaretskii via Gdb <gdb@sourceware.org>
Subject: Re: [question] If the code format is wrong, the _initialize_xxx functions cannot be generated?
Date: Mon, 30 Jan 2023 20:10:27 -0600 [thread overview]
Message-ID: <CAF9ehCUsQkjqzUxv3boSCOK4fJycN+CF6242dtehY0F1szHyqw@mail.gmail.com> (raw)
In-Reply-To: <ba5e0174-bcda-beff-98f4-441bcf628011@simark.ca>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
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 2:10 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 [this message]
2023-01-31 3:31 ` hilbert
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=CAF9ehCUsQkjqzUxv3boSCOK4fJycN+CF6242dtehY0F1szHyqw@mail.gmail.com \
--to=joel@rtems.org \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
--cc=swdtian@163.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).