public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9356: [3.4 regression] [New parser] internal compiler error in validate_nonmember_using_decl, at cp/delc2.c:4179 Date: Fri, 17 Jan 2003 20:56:00 -0000 [thread overview] Message-ID: <20030117205604.4618.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9356; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Rick Moseley <rmoseley@redhat.com> Cc: gcc-bugs@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/9356: [3.4 regression] [New parser] internal compiler error in validate_nonmember_using_decl, at cp/delc2.c:4179 Date: Fri, 17 Jan 2003 14:49:18 -0600 (CST) > You are right sir. I have a header file that had the following 2 includes: > > #include <g2c.h> > #include <iostream> > > Reversing the order of those includes fixed the problem. But it's still a bug that we get an internal compiler error on the code, however bogus it may be. (Which reminds me that I forgot to set ice-on-illegal for this report... Will fix.) W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-01-17 20:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-17 20:56 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-22 18:48 mmitchel 2003-01-17 20:56 Rick Moseley 2003-01-17 20:28 bangerth
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=20030117205604.4618.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).