From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9B5933948801; Fri, 20 Mar 2020 16:06:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9B5933948801 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584720403; bh=itx2FPt2MU7dfKAPiRq71pcx81vsDkfhRyem13JoUfk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=y5lXqbrOiHXY7CXXLLRbjhGaA1U4wpkToNLhc5KgpCZA+4/PYJ6nNoJQP6Rmp8VCu nqrYCd2bAYm21/w/RQtTHV0oAV7oY8oM8DT73MJG4br3lBvqeDPehW2+7TJzZwTq2G +06//XZ5yfmjXHyLMy+T7mUroSqz7JHzAQNql0Iw= From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/94230] provide an option to change the size limitation for -Wmisleading-indent Date: Fri, 20 Mar 2020 16:06:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: dmalcolm at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 16:06:43 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94230 --- Comment #6 from David Malcolm --- I'm not sure this has a changed a lot "recently"; I did 2-3 years ago IIRC. The warning occurs when we have location_t > LINE_MAP_MAX_LOCATION_WITH_COLS which means that we've run out of values for expressing locations. If you have a huge workload, one possible workaround would be to disable ra= nge 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'm not sure if either of these are good ideas though.=