public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: te200@eng.cam.ac.uk
To: gcc-gnats@gcc.gnu.org
Subject: c++/10150: Internal compiler error generated by stupid template code
Date: Wed, 19 Mar 2003 14:26:00 -0000	[thread overview]
Message-ID: <20030319142535.12831.qmail@sources.redhat.com> (raw)


>Number:         10150
>Category:       c++
>Synopsis:       Internal compiler error generated by stupid template code
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 19 14:26:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Tom Evans
>Release:        3.2.1
>Organization:
>Environment:
djgpp, Win98.
>Description:
When I try to compile the code given, I get an internal compiler error.  I can't test it on a proper gcc easily, so this is only in djgpp.  So if you can't reproduce it straight away, chuck this report in the bin.

Note no workaround is needed - the code is stupid, I just thought it still shouldn't generate an internal error.

Attempted compile with 'gxx -c a.cc', got:

a.cc: In instantiation of `Pow<0>::In<0>':
a.cc:9:   instantiated from here
a.cc:9: Internal compiler error in resolve_offset_ref, at cp/init.c:1891
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
template <int N>
struct Pow {
  template <int Val>
  struct In {
    enum { value = Val * Pow<N-1>::In };
  };
};

Pow<0>::In<0> a;
>Fix:

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


             reply	other threads:[~2003-03-19 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 14:26 te200 [this message]
2003-03-19 14:47 lerdsuwa

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=20030319142535.12831.qmail@sources.redhat.com \
    --to=te200@eng.cam.ac.uk \
    --cc=gcc-gnats@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).