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++/9868: [3.3/3.4 regression] ICE in c_expand_expr when qualifying member variable Date: Thu, 27 Feb 2003 17:06:00 -0000 [thread overview] Message-ID: <20030227170601.13789.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9868; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Michael Matz <matz@suse.de> Cc: china@thewrittenword.com, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/9868: [3.3/3.4 regression] ICE in c_expand_expr when qualifying member variable Date: Thu, 27 Feb 2003 10:56:38 -0600 (CST) > > Correct, at least close. I had a problem with 9524 before, and still have: > > it doesn't ICE on mainline for me. > > Ahh, yes. I forgot. It would be interesting to know in which way our > compilers differ, that even the frontend behaves differently. Hmm. Valid question. I am building straight from CVS, on a SuSE 8 box. Are you using additional SuSE patches? At any rate, 9868 seems to be a superset of the problem in 9524, so should 9868 be fixed, this would likely cure 9524 as well, and for both of us. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-02-27 17:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-27 17:06 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-10 21:12 jason 2003-03-06 21:18 jason 2003-02-27 17:26 Michael Matz 2003-02-27 16:56 Michael Matz 2003-02-27 16:16 Wolfgang Bangerth 2003-02-27 16:06 Michael Matz 2003-02-27 15:30 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=20030227170601.13789.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).