public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54928] Infinite output with after ICE with macro Date: Tue, 16 Oct 2012 18:06:00 -0000 [thread overview] Message-ID: <bug-54928-4-hsGml9A3C2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54928-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54928 --- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-10-16 18:05:52 UTC --- Created attachment 28457 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28457 better fix The code is re-using the diagnostic passed as an argument to produce new diagnostics, and by saving/reloading values on it. But we actually only need to modify things once, and if we use a new diagnostic struct, we don't need to touch the original. Of course, we should still not print the caret and macro expansion in internal_error, but that is a bit more complicated.
next prev parent reply other threads:[~2012-10-16 18:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-14 23:17 [Bug c++/54928] New: " cas43 at cs dot stanford.edu 2012-10-15 0:14 ` [Bug c++/54928] " manu at gcc dot gnu.org 2012-10-15 8:59 ` paolo.carlini at oracle dot com 2012-10-15 9:17 ` manu at gcc dot gnu.org 2012-10-15 9:25 ` paolo.carlini at oracle dot com 2012-10-15 9:27 ` manu at gcc dot gnu.org 2012-10-15 9:31 ` manu at gcc dot gnu.org 2012-10-16 18:00 ` manu at gcc dot gnu.org 2012-10-16 18:06 ` manu at gcc dot gnu.org [this message] 2012-10-16 22:26 ` paolo.carlini at oracle dot com 2012-10-24 22:02 ` manu at gcc dot gnu.org 2012-10-24 22:25 ` manu 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-54928-4-hsGml9A3C2@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).