public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Art <pinaart@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8942: internal compiler error: in ggc_set_mark, at ggc-page.c:981
Date: Tue, 17 Dec 2002 23:16:00 -0000	[thread overview]
Message-ID: <20021218071602.32152.qmail@sources.redhat.com> (raw)

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

From: Art <pinaart@yahoo.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8942: internal compiler error: in ggc_set_mark, at ggc-page.c:981
Date: Tue, 17 Dec 2002 23:13:18 -0800 (PST)

 --- bangerth@dealii.org wrote:
 > Synopsis: internal compiler error: in ggc_set_mark, at ggc-page.c:981
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Mon Dec 16 11:31:17 2002
 > State-Changed-Why:
 >     I cannot reproduce this with a snapshot from last week. Could
 >     you possibly try whether the bug still occurs on your system
 >     with a newer version of gcc?
 >     
 >     Thanks
 >       W.
 
 Thanks, W.
 
 I downloaded and rebuilt gcc 3.4 from the cvs tree and am no longer
 experiencing any problems with the compiler.
 
 Art
 
 __________________________________________________
 Do you Yahoo!?
 Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
 http://mailplus.yahoo.com


             reply	other threads:[~2002-12-18  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 23:16 Art [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18  5:17 reichelt
2002-12-16 11:31 bangerth
2002-12-14 10:56 pinaart

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=20021218071602.32152.qmail@sources.redhat.com \
    --to=pinaart@yahoo.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).