From: Tom Tromey <tom@tromey.com>
To: Joel Sherrill <joel@rtems.org>
Cc: Simon Marchi <simark@simark.ca>, 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: Wed, 08 Feb 2023 12:58:14 -0700 [thread overview]
Message-ID: <874jrw0w15.fsf@tromey.com> (raw)
In-Reply-To: <CAF9ehCUsQkjqzUxv3boSCOK4fJycN+CF6242dtehY0F1szHyqw@mail.gmail.com> (Joel Sherrill's message of "Mon, 30 Jan 2023 20:10:27 -0600")
Joel> FWIW RTEMS also has its own formatting quirks and clang-format appears to
Joel> be within one option for us now. One of our core folks was considering
Joel> addressing that one.
Joel> They get better and better so worth looking periodically.
I try periodically for gdb. Today I updated to clang-format 14, went
through all the options, and tried again.
I don't really understand what I'm doing, though, so it's not completely
clear the results are definitive. But anyway, my experience has been
pretty negative. There are a lot of minor differences that I don't
really care about, but the way bin-packing works for function arguments
leaves some calls unreadable to me.
I filed https://sourceware.org/bugzilla/show_bug.cgi?id=30098 to track
our progress here.
Tom
prev parent reply other threads:[~2023-02-08 19:58 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
2023-02-08 19:58 ` Tom Tromey [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=874jrw0w15.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=joel@rtems.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).