public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dmitri Lenev <dlenev@spylog.ru>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5125: both g++ 3.0.1 and 2.95.3 crash with internal error when trying compile template method with parameter pointer to method
Date: Sat, 15 Dec 2001 07:56:00 -0000	[thread overview]
Message-ID: <20011215155601.20862.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

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

From: Dmitri Lenev <dlenev@spylog.ru>
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/5125: both g++ 3.0.1 and 2.95.3 crash with internal error when trying compile template method with parameter pointer to method
Date: Sat, 15 Dec 2001 18:53:23 +0300

 Thanks a lot. 
 
 So it is ice-on-illegal-code sort of bug. :-)
 
 Anyway i have resolved the problem by slightly changing my design approach...
 
 * rodrigc@gcc.gnu.org <rodrigc@gcc.gnu.org> [01/12/15 18:23]:
 > Synopsis: both g++ 3.0.1 and 2.95.3 crash with internal error when trying compile template method with parameter pointer to method
 > 
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: rodrigc
 > State-Changed-When: Sat Dec 15 07:21:04 2001
 > State-Changed-Why:
 >     The compiler should probably not ICE, but your
 >     code example is illegal.  You made a spelling mistake in
 >     one of the parameter names:
 >     
 >     --- t.cc.orig   Sat Dec 15 10:19:55 2001
 >     +++ t.cc        Sat Dec 15 10:20:01 2001
 >     @@ -49,7 +49,7 @@
 >        SerializationStream::serializeMember (unsigned int member, const I & item,
 >                                             size_t (I::
 >                                                     *serialization_function)
 >     -                                       (SerializationSream & stream) const)
 >     +                                       (SerializationStream & stream) const)
 >      {
 >        serialize (member);
 >        size_t valueSize = item.*serialization_function (*this);
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5125
 
 -- 
 ó Õ×ÁÖÅÎÉÅÍ, äÍÉÔÒÉÊ ìÅÎÅ×.


             reply	other threads:[~2001-12-15 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15  7:56 Dmitri Lenev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29  9:15 nathan
2001-12-29  7:32 nathan
2001-12-15  7:21 rodrigc
2001-12-15  7:06 dlenev

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=20011215155601.20862.qmail@sources.redhat.com \
    --to=dlenev@spylog.ru \
    --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).