public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94230] provide an option to change the size limitation for -Wmisleading-indent
Date: Mon, 30 Mar 2020 20:31:35 +0000 [thread overview]
Message-ID: <bug-94230-4-MUuTKSja5m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94230-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94230
--- Comment #7 from qinzhao at gcc dot gnu.org ---
(In reply to David Malcolm from comment #6)
> If you have a huge workload, one possible workaround would be to disable
> range tracking, perhaps tweaking line_table->default_range_bits, which would
> give you a bit more "headroom". IIRC we don't currently expose a way to do
> this, and probably some extra code would be needed. It's currently
> hardcoded to 5.
>
> Perhaps some kind of -fno-location-ranges? It could either:
> (a) don't attempt to store location ranges (would probably have to disable
> e.g. fix-it hints)
> (b) set line_table->default_range_bits to 0, so that all ranges have to go
> to the ad-hoc table, but buying space for more locations.
I have tried the above (2) to set the line_table->default_range_bits to 0. and
used
this GCC to compile our huge application with -Wmisleading-indent, this time,
the compiler works without the warning. and there are also some proper
misleading-indent warning were emitted.
So, I'd like to add one new gcc option -fno-location-range, whose
implementation is to set line_table->default_range_bits to 0 to save more space
for column tracking.
Is this good to go?
next prev parent reply other threads:[~2020-03-30 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 21:58 [Bug c/94230] New: " qinzhao at gcc dot gnu.org
2020-03-19 22:05 ` [Bug c/94230] " jakub at gcc dot gnu.org
2020-03-20 14:57 ` qinzhao at gcc dot gnu.org
2020-03-20 14:59 ` jakub at gcc dot gnu.org
2020-03-20 15:02 ` qinzhao at gcc dot gnu.org
2020-03-20 15:21 ` jakub at gcc dot gnu.org
2020-03-20 16:06 ` dmalcolm at gcc dot gnu.org
2020-03-30 20:31 ` qinzhao at gcc dot gnu.org [this message]
2020-04-06 15:23 ` qinzhao at gcc dot gnu.org
2020-05-06 17:46 ` cvs-commit at gcc dot gnu.org
2020-05-06 18:41 ` qinzhao at gcc dot gnu.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-94230-4-MUuTKSja5m@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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: 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).