public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 06 May 2020 17:46:49 +0000 [thread overview] Message-ID: <bug-94230-4-tBN2hgGonf@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 #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Qing Zhao <qinzhao@gcc.gnu.org>: https://gcc.gnu.org/g:530b44094354758d0dea5374188caa6863647114 commit r11-146-g530b44094354758d0dea5374188caa6863647114 Author: qing zhao <qing.zhao@oracle.com> Date: Wed May 6 10:46:09 2020 -0700 add a new option -flarge-source-files. gcc/ChangeLog: PR c/94230 * common.opt: Add -flarge-source-files. * doc/invoke.texi: Document it. * toplev.c (process_options): set line_table->default_range_bits to 0 when flag_large_source_files is true. gcc/c-family/ChangeLog: PR c/94230 * c-indentation.c (get_visual_column): Add a hint to use the new -flarge-source-files option. gcc/testsuite/ChangeLog: PR c/94230 * gcc.dg/plugin/location-overflow-test-1.c (fn_1): New message to provide hint to use the new -flarge-source-files option.
next prev parent reply other threads:[~2020-05-06 17:46 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 2020-04-06 15:23 ` qinzhao at gcc dot gnu.org 2020-05-06 17:46 ` cvs-commit at gcc dot gnu.org [this message] 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-tBN2hgGonf@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: linkBe 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).