From: Qing Zhao <QING.ZHAO@ORACLE.COM>
To: dmalcolm@redhat.com, jakub@redhat.com
Cc: gcc-patches@gcc.gnu.org
Subject: Fwd: PING [PATCH][gcc][PR94230]provide an option to change the size limitation for -Wmisleading-indent
Date: Wed, 15 Apr 2020 15:30:26 -0500 [thread overview]
Message-ID: <DD50162E-0804-4995-B2EF-A7FAAEEDCBD4@ORACLE.COM> (raw)
In-Reply-To: <47B8948D-C9BA-41EC-B55B-AF8117E79C50@ORACLE.COM>
Ping.
We need this patch for our product building.
thanks.
Qing
> Begin forwarded message:
>
> From: Qing Zhao via Gcc-patches <gcc-patches@gcc.gnu.org>
> Subject: PING [PATCH][gcc][PR94230]provide an option to change the size limitation for -Wmisleading-indent
> Date: April 8, 2020 at 2:39:22 PM CDT
> To: dmalcolm@redhat.com, jakub@redhat.com
> Cc: gcc-patches@gcc.gnu.org
> Reply-To: Qing Zhao <QING.ZHAO@ORACLE.COM>
>
> Hi,
>
> Please take a look at the attached patch and let me know your comments.
>
> Thanks.
>
> Qing
>
> gcc/ChangeLog:
>
> 2020-04-03 qing zhao <qing.zhao@oracle.com>
>
> * common.opt: Add -flocation-ranges.
> * doc/invoke.texi: Document it.
> * toplev.c (process_options): set line_table->default_range_bits
> to 0 when flag_location_ranges is false.
>
>
>
>> Begin forwarded message:
>>
>> From: Qing Zhao via Gcc-patches <gcc-patches@gcc.gnu.org>
>> Subject: [PATCH][gcc][PR94230]provide an option to change the size limitation for -Wmisleading-indent
>> Date: April 3, 2020 at 2:55:53 PM CDT
>> To: dmalcolm@redhat.com, jakub@redhat.com
>> Cc: gcc-patches@gcc.gnu.org
>> Reply-To: Qing Zhao <QING.ZHAO@ORACLE.COM>
>>
>> Hi, David and Jakub,
>>
>> Per the discussion we had for PR94230: provide an option to change the size limitation for -Wmisleading-indent
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94230 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94230>
>>
>> I come up with the following simple patch per David’s suggestion:
>>
>> Provide a new first class option -flocation-ranges to control enabling/disablng range tracking when recording source locations.
>> The default value for this option is enabling the range tracking.
>>
>> When specify -fno-location-ranges, disable the range tracking to save space for column tracking.
>>
>> I have tested this GCC to build our huge application by adding -fno-location-ranges, the whole build completed without any issue. and
>> -Wmisleading-indent also emitted several helpful warning message during building.
>>
>> I am running bootstrap right now.
>>
>> Could you please take a look at the attached patch?
>>
>> thanks.
>>
>> Qing
>>
>>
>>
>>
>
next prev parent reply other threads:[~2020-04-15 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 19:55 Qing Zhao
2020-04-08 19:39 ` PING " Qing Zhao
2020-04-15 20:30 ` Qing Zhao [this message]
2020-04-21 14:04 ` Richard Sandiford
2020-04-21 15:21 ` David Malcolm
2020-04-21 18:46 ` Richard Sandiford
2020-04-22 14:22 ` Qing Zhao
2020-04-23 14:41 ` [Version 2][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-23 18:27 ` Richard Sandiford
2020-04-23 19:52 ` Qing Zhao
2020-04-23 21:05 ` [Version 3][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-23 22:13 ` David Malcolm
2020-04-24 22:22 ` [Version 4][PATCH][gcc][PR94230]provide " Qing Zhao
2020-04-24 22:36 ` David Malcolm
2020-04-27 14:23 ` Qing Zhao
2020-05-06 18:40 ` Committed [Version 3][PATCH][gcc][PR94230]provide " Qing Zhao
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=DD50162E-0804-4995-B2EF-A7FAAEEDCBD4@ORACLE.COM \
--to=qing.zhao@oracle.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).