public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/279: g++ internal compiler error w/test case
Date: Fri, 16 Nov 2001 21:27:00 -0000	[thread overview]
Message-ID: <20011121113601.1396.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/279; it has been noted by GNATS.

From: nathan@gcc.gnu.org
To: dennis@funkplanet.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
  gcc-prs@gcc.gnu.org, martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/279: g++ internal compiler error w/test case
Date: 21 Nov 2001 11:33:52 -0000

 Synopsis: g++ internal compiler error w/test case
 
 State-Changed-From-To: analyzed->closed
 State-Changed-By: nathan
 State-Changed-When: Wed Nov 21 03:33:51 2001
 State-Changed-Why:
     this is fixed on the mainline, which reports,
     nathan@uha:188>./cc1plus -ansi -pedantic -quiet incomming/279.ii 
     incomming/279.ii:19: warning: ISO C++ forbids declaration of `operator[]' with 
        no type
     incomming/279.ii:19: `const int& operator[](int)' must be a nonstatic member 
        function
     incomming/279.ii:19: `const int& operator[](int)' must take exactly two 
        arguments
     incomming/279.ii: In function `const int& operator[](int)':
     incomming/279.ii:20: `_foo' undeclared (first use this function)
     incomming/279.ii:20: (Each undeclared identifier is reported only once for each 
        function it appears in.)
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=279&database=gcc


             reply	other threads:[~2001-11-21 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 21:27 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-16 21:26 nathan

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=20011121113601.1396.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --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).