public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/4633: g++ 3.0.1 bogus error on nested partial specialization
@ 2001-10-22  9:17 lerdsuwa
  0 siblings, 0 replies; 3+ messages in thread
From: lerdsuwa @ 2001-10-22  9:17 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, nobody, sebor

Synopsis: g++ 3.0.1 bogus error on nested partial specialization

State-Changed-From-To: open->analyzed
State-Changed-By: lerdsuwa
State-Changed-When: Mon Oct 22 09:17:48 2001
State-Changed-Why:
    Confirm as a bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4633&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c++/4633: g++ 3.0.1 bogus error on nested partial specialization
@ 2003-01-03 15:27 neroden
  0 siblings, 0 replies; 3+ messages in thread
From: neroden @ 2003-01-03 15:27 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, nobody, sebor

Synopsis: g++ 3.0.1 bogus error on nested partial specialization

State-Changed-From-To: analyzed->closed
State-Changed-By: neroden
State-Changed-When: Fri Jan  3 07:27:50 2003
State-Changed-Why:
    Fixed by the new parser.  Testcase in g++.dg/template/nested1.C

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4633


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c++/4633: g++ 3.0.1 bogus error on nested partial specialization
@ 2001-10-20 14:46 sebor
  0 siblings, 0 replies; 3+ messages in thread
From: sebor @ 2001-10-20 14:46 UTC (permalink / raw)
  To: gcc-gnats

>Number:         4633
>Category:       c++
>Synopsis:       g++ 3.0.1 bogus error on nested partial specialization
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 20 14:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     sebor@roguewave.com
>Release:        3.0.1
>Organization:
>Environment:
i386-pc-solaris2.8
>Description:
The code snippet below fails to compile with g++ 3.0.1,
giving an obviously bogus error.

Regards
Martin

>How-To-Repeat:
$ cat t.cpp ; g++ -v ; g++ t.cpp
struct N;

template <class T, class U>
struct L { };

template <class T, template <class, class> class>
struct S;

template <class T, template <class, class> class P>
struct S<L<T, N>, P> { typedef L<T, N> Result; };

template <class T, class U, template <class, class> class P>
struct S<L<T, U>, P>
{
    template <class> struct M;
    template <class V> struct M<L<V, N> > { typedef V Y; };

    template <class V, class W>
    struct M<L<V, W> > { typedef typename P<V, typename M<W>::Y>::Y Y; };

    template <class, class> struct R;
    template <class V> struct R<L<V, N>, V> { typedef N Y; };
    template <class V, class W> struct R<L<V, W>, V> { typedef W Y; };

    template <class V, class W, class X>
    struct R<L<V, W>, X> { typedef L<V, typename R<W, X>::Y> Y; };

    typedef typename M<L<T, U> >::Y X;
    typedef L<X, typename S<typename R<L<T, U>, X>::Y, P>::Result> Result;
};

Reading specs from /usr/local/gcc-3.0.1/lib/gcc-lib/i386-pc-solaris2.8/3.0.1/specs
Configured with: ../gcc-3.0.1/configure --prefix=/usr/local/gcc-3.0.1 --enable-languages=c,c++ --enable-threads
Thread model: posix
gcc version 3.0.1
t.cpp:28: declaration of `typedef typename S<L<T, U>, P>::M<L<T, U> >::Y S<L<T, 
   U>, P>::X'
t.cpp:25: changes meaning of `X' from `class X'
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-01-03 15:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-22  9:17 c++/4633: g++ 3.0.1 bogus error on nested partial specialization lerdsuwa
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03 15:27 neroden
2001-10-20 14:46 sebor

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).