public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/94229] New: more clarification on the warning message from -Wmisleading-indent
@ 2020-03-19 21:51 qinzhao at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: qinzhao at gcc dot gnu.org @ 2020-03-19 21:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94229
Bug ID: 94229
Summary: more clarification on the warning message from
-Wmisleading-indent
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: qinzhao at gcc dot gnu.org
Target Milestone: ---
gcc issues the following warning message for -Wmisleading-indentation:
test.c:632: note: -Wmisleading-indentation is disabled from this point
onwards, since column-tracking was disabled due to the size of the
code/headers
For a file test.c on its line #632, which looks very confusing to the user who
got this message because 632 lines in a file is not big at all.
is it possible to make the warning message more clear on why the size limit is
met to help the user understand this better?
>From my understanding of the gcc code in libcpp/line-map.[hc], looks like that
the "size" here refs to source_location, and the source_location encoded both
line num info and column num info.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-03-19 21:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-19 21:51 [Bug c/94229] New: more clarification on the warning message from -Wmisleading-indent qinzhao at gcc dot gnu.org
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).