public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Juan Carlos Arevalo-Baeza <jcab@JCABs-Rumblings.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5639: Internal compiler error on lifted class
Date: Mon, 13 May 2002 09:26:00 -0000	[thread overview]
Message-ID: <20020513162602.7769.qmail@sources.redhat.com> (raw)

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

From: Juan Carlos Arevalo-Baeza <jcab@JCABs-Rumblings.com>
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++/5639: Internal compiler error on lifted class
Date: Mon, 13 May 2002 09:20:51 -0700

 On 11 May 2002 17:20:28 -0000, rodrigc@gcc.gnu.org wrote:
 >Synopsis: Internal compiler error on lifted class
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: rodrigc
 >State-Changed-When: Sat May 11 10:20:26 2002
 >State-Changed-Why:
 >=A0=A0Your attachment got corrupted and is not complete.
 >=A0=A0Can you send it to me directly?
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&da=
 tabase=3Dgcc&pr=3D5639
 
    I see this file got truncated somehow. I don't keep the=
  original around. This is months old... Hmmm... I do keep the=
  original "c_grammar.cpp", I think. I'll try to make it happen=
  again when I have a moment. I just don't remember the exact=
  details. Be patient :)
 
 =A0=A0=A0Salutaciones,
 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0JCAB
 email: jcab@JCABs-Rumblings.com
 ICQ: 10913692 @WORK: 101728263
 WWW: http://www.JCABs-Rumblings.com
 


             reply	other threads:[~2002-05-13 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13  9:26 Juan Carlos Arevalo-Baeza [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-11 10:20 rodrigc
2002-02-08 23:46 jcab

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=20020513162602.7769.qmail@sources.redhat.com \
    --to=jcab@jcabs-rumblings.com \
    --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).