public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jgibbs@bluearc.com,
mdorey@bluearc.com, nobody@gcc.gnu.org
Subject: Re: c++/9420: [3.2/3.3/3.4 regression] incomplete type incorrectly reported
Date: Thu, 23 Jan 2003 17:13:00 -0000 [thread overview]
Message-ID: <20030123171355.16804.qmail@sources.redhat.com> (raw)
Old Synopsis: [regression over 2.95] incomplete type incorrectly reported
New Synopsis: [3.2/3.3/3.4 regression] incomplete type incorrectly reported
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Jan 23 17:13:55 2003
State-Changed-Why:
True. Very weird problem:
--------------------------
enum { E };
template <typename T> struct A {
static const int a = (E < 0);
};
template <typename T> class B {
A<int> b;
};
struct C {
C(B<int>);
};
int operator<(C, C);
A<int> c;
----------------------------
Changing any bit of the code makes the bug go away (e.g.
changing op< to function foo). Used to work with 2.95, but
does no longer with 3.2.2 and 3.3 (just accidentially
ruined my 3.4 installation, but likely to show same problem).
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9420
next reply other threads:[~2003-01-23 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 17:13 bangerth [this message]
2003-01-23 18:20 nathan
2003-03-13 19:14 jason
2003-03-13 19:29 jason
2003-03-13 20:26 jason
2003-03-13 21:41 jason
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=20030123171355.16804.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=jgibbs@bluearc.com \
--cc=mdorey@bluearc.com \
--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: 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).