public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, t-gcc@snowelm.com Subject: Re: c++/9474: [3.2/3.3/3.4 regression] GCC freezes in compiling a weird code mixing <iostream> and <iostream.h> Date: Tue, 28 Jan 2003 14:01:00 -0000 [thread overview] Message-ID: <20030128140122.10553.qmail@sources.redhat.com> (raw) Old Synopsis: GCC freezes in compiling a weird code mixing <iostream> and <iostream.h> New Synopsis: [3.2/3.3/3.4 regression] GCC freezes in compiling a weird code mixing <iostream> and <iostream.h> State-Changed-From-To: open->analyzed State-Changed-By: cae State-Changed-When: Tue Jan 28 14:01:22 2003 State-Changed-Why: Confirmed. Here's a reduced testcase, probably illegal but I'm not 100% sure. This is actually an infinite loop in gcc, not an ICE but I'll leave this in ICE on illegal for the moment. ---------- cut ---------- namespace X { typedef struct { } x; }; typedef X::x x; using X::x; ---------- cut ---------- This is a regression from 2.95 which issued this error: t.cc:6: using directive `x' introduced ambiguous type `X::x' The loop is in the function original_type in gcc/cp/typeck.c because the decl for ::x references itself in DECL_ORIGINAL_TYPE (TYPE_NAME (x)). regards Christian http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9474
next reply other threads:[~2003-01-28 14:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-28 14:01 ehrhardt [this message] 2003-03-12 3:33 mmitchel
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=20030128140122.10553.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=t-gcc@snowelm.com \ /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).