public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/97932] [8/9/10/11 Regression] Preprocessor, generated error dumps most of the source file, not just one line by r6-5941
Date: Wed, 03 Feb 2021 13:07:44 +0000 [thread overview]
Message-ID: <bug-97932-4-oEFERSj4er@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97932-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97932
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
David, do you think you could have a look? Perhaps having some upper limit on
the number of lines and not print the source if it would be too many lines?
next prev parent reply other threads:[~2021-02-03 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 8:27 [Bug c/97932] New: Preprocessor, generated error dumps most of the source file, not just one line lance.delahaye at gmail dot com
2020-11-21 9:21 ` [Bug c/97932] " pinskia at gcc dot gnu.org
2020-11-21 10:19 ` lance.delahaye at gmail dot com
2020-11-21 10:26 ` lance.delahaye at gmail dot com
2020-11-21 14:34 ` [Bug c/97932] [8/9/10/11 Regression] Preprocessor, generated error dumps most of the source file, not just one line by r6-5941 hjl.tools at gmail dot com
2020-11-23 7:31 ` rguenth at gcc dot gnu.org
2021-02-03 13:07 ` jakub at gcc dot gnu.org [this message]
2021-02-03 14:21 ` dmalcolm at gcc dot gnu.org
2021-02-04 20:23 ` cvs-commit at gcc dot gnu.org
2021-02-04 20:30 ` [Bug c/97932] [8/9/10 " dmalcolm at gcc dot gnu.org
2021-05-14 9:54 ` [Bug c/97932] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:18 ` rguenth at gcc dot gnu.org
2022-05-27 9:43 ` [Bug c/97932] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07 9:13 ` rguenth 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-97932-4-oEFERSj4er@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).