From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simark@simark.ca>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix indentation (and clang warning) in c-lang.c
Date: Tue, 17 Dec 2019 19:41:00 -0000 [thread overview]
Message-ID: <d22c6e95-7c69-43c2-20c4-f4714f4307eb@redhat.com> (raw)
In-Reply-To: <6663a453-29d5-e38f-4f47-30c2ff18c331@simark.ca>
On 12/17/19 7:39 PM, Simon Marchi wrote:
> On 2019-12-17 2:24 p.m., Pedro Alves wrote:
>> Curious. Are you saying that that changed recently in clang? I wonder
>> whether clang's warning catches this case on purpose, or whether it's
>> a regression. I asked David Malcolm, who added that warning to GCC, and he
>> said that GCC's implementation respects tab stops, so small numbers of
>> leading spaces before a tab are effectively ignored.
>
> The warning appears to be new in clang 10, because it doesn't exist in clang 9:
>
> $ clang++ test.cpp -Wmisleading-indentation
> warning: unknown warning option '-Wmisleading-indentation'; did you mean '-Wbinding-in-condition'? [-Wunknown-warning-option]
>
> I can't tell if it's on purpose or not. I wonder if it's worth opening a bug
> on clang's bugzilla to ask whether it's intentional or not, it might help them
> tweak the warning before it's officially released...
Yes, I think it's worth it. Part of the point of using pre release compilers
is to catch&fix issues before they are released.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-12-17 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 23:36 Simon Marchi
2019-12-16 23:50 ` Simon Marchi
2019-12-17 19:24 ` Pedro Alves
2019-12-17 19:39 ` Simon Marchi
2019-12-17 19:41 ` Pedro Alves [this message]
2019-12-17 19:53 ` Simon Marchi
2019-12-18 18:28 ` Simon Marchi
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=d22c6e95-7c69-43c2-20c4-f4714f4307eb@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.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