public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mmitchell@usa.net>
To: Ross Alexander <rossa@stimpy.math.auckland.ac.nz>
Cc: egcs@cygnus.com, law@cygnus.com, Jason Merrill <jason@cygnus.com>
Subject: Error in 971122 i686-pc-linux-gnu
Date: Thu, 27 Nov 1997 22:49:00 -0000	[thread overview]
Message-ID: <199711272141.VAA00141@quickstep.stanford.edu> (raw)
In-Reply-To: <199711280306.QAA11798@stimpy.math.auckland.ac.nz>

Jason et. al. --

  I wonder if the implicit typename stuff should be disabled for the
release.  There seem to be a lot of internal errors being reported in
cases where the users should have used 'typename'.  (Ross, your code
is illegal: you have to say 'typename X::A'.)  At the very least, we
could issue a warning on this so that users would have a hint about
what they might do to avoid triggering the crash.

>>>>> "Ross" == Ross Alexander <rossa@stimpy.math.auckland.ac.nz> writes:

    Ross> I get an error 9 in the following code
    Ross> ----------------------------------------------------------------------
    Ross> template <class X> int foo<X> (X a) { X::A b; // = a; }
    Ross> ----------------------------------------------------------------------
    Ross> stimpy:~$ g++ -v test.cc Reading specs from
    Ross> experimental).  test.cc:2: Internal compiler error 9.
    Ross> test.cc:2: Please submit a full bug report to
    Ross> `egcs-bugs@cygnus.com'.  stimpy:~$
    Ross> ----------------------------------------------------------------------

-- 
Mark Mitchell		mmitchell@usa.net
Stanford University	http://www.stanford.edu


  reply	other threads:[~1997-11-27 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-27 19:10 Ross Alexander
1997-11-27 22:49 ` Mark Mitchell [this message]
1997-11-28  1:30   ` Jason Merrill
1997-11-28  2:23   ` Jason Merrill
1997-12-01 18:46     ` C9X draft online Oleg Krivosheev

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=199711272141.VAA00141@quickstep.stanford.edu \
    --to=mmitchell@usa.net \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    --cc=law@cygnus.com \
    --cc=rossa@stimpy.math.auckland.ac.nz \
    /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).