public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/6069: GC failure w/ THREAD_LOCAL_ALLOC
Date: Tue, 26 Mar 2002 15:06:00 -0000	[thread overview]
Message-ID: <20020326230232.12348.qmail@sources.redhat.com> (raw)


>Number:         6069
>Category:       libgcj
>Synopsis:       GC failure w/ THREAD_LOCAL_ALLOC
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 26 15:06:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        current 3.1 branch
>Organization:
>Environment:

>Description:
Read this thread:

http://gcc.gnu.org/ml/java/2002-03/msg00443.html

There is a test case in the first message.
This is very important for 3.1.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-26 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 15:06 tromey [this message]
2002-03-29 14:42 tromey

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=20020326230232.12348.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-gnats@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).