public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/30098] Keep trying clang-format Date: Wed, 08 Feb 2023 20:07:38 +0000 [thread overview] Message-ID: <bug-30098-4717-nnf3L35sJn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30098-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30098 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- BTW there are a bunch of FIXMEs in the config file. I don't really know how the penalty system works so maybe that can be improved too. Sometimes clang-format makes bad decisions. One example I'm looking at is if you have an 'if' that is a series of clauses joined by '&&', sometimes it is clearest to put each such clause on its own line. However clang-format does this: @@ -194,10 +193,8 @@ eq_bfd (const void *a, const void *b) = (const struct gdb_bfd_cache_search *) b; struct gdb_bfd_data *gdata = (struct gdb_bfd_data *) bfd_usrdata (abfd); - return (gdata->mtime == s->mtime - && gdata->size == s->size - && gdata->inode == s->inode - && gdata->device_id == s->device_id + return (gdata->mtime == s->mtime && gdata->size == s->size + && gdata->inode == s->inode && gdata->device_id == s->device_id && strcmp (bfd_get_filename (abfd), s->filename) == 0); } -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-08 20:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 19:57 [Bug build/30098] New: " tromey at sourceware dot org 2023-02-08 20:00 ` [Bug build/30098] " tromey at sourceware dot org 2023-02-08 20:05 ` tromey at sourceware dot org 2023-02-08 20:07 ` tromey at sourceware dot org [this message] 2023-02-08 20:09 ` tromey at sourceware dot org 2023-02-08 20:10 ` tromey at sourceware dot org 2023-02-08 20:32 ` simark at simark dot ca 2023-02-08 21:31 ` jan at vrany dot io 2023-02-08 22:27 ` sam at gentoo dot org 2023-02-08 23:57 ` tromey at sourceware dot org 2023-08-03 16:53 ` tromey at sourceware dot org
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=bug-30098-4717-nnf3L35sJn@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).