public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hesham@bestweb.net, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org Subject: Re: java/8003: gcj segfaults on simple java line of code Date: Sun, 22 Sep 2002 23:13:00 -0000 [thread overview] Message-ID: <20020923061303.23927.qmail@sources.redhat.com> (raw) Synopsis: gcj segfaults on simple java line of code Responsible-Changed-From-To: unassigned->tromey Responsible-Changed-By: tromey Responsible-Changed-When: Sun Sep 22 23:13:03 2002 Responsible-Changed-Why: I'm handling this. State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Sun Sep 22 23:13:03 2002 State-Changed-Why: Thanks for the report. I agree this is a bug. I sent a patch for approval. In general this sort of thing hasn't gotten a lot of scrutiny. gcj probably has more bugs like this one. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8003
next reply other threads:[~2002-09-23 6:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-22 23:13 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-08 11:06 tromey 2002-09-22 9:56 hesham
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=20020923061303.23927.qmail@sources.redhat.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hesham@bestweb.net \ --cc=java-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: linkBe 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).