public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ngmlinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/5487] arm-linux-gcj cross-compiler generates bad assembler-code
Date: Thu, 01 Sep 2005 19:52:00 -0000	[thread overview]
Message-ID: <20050901195204.29579.qmail@sourceware.org> (raw)
In-Reply-To: <20020125014600.5487.jsantala@tml.hut.fi>


------- Additional Comments From ngmlinux at gmail dot com  2005-09-01 19:52 -------
Subject: Re:  arm-linux-gcj cross-compiler generates bad assembler-code

> > (gdb) bt
> > #0  GC_push_all_eager (bottom=0x0, top=0x390a8 "") at
> > ../../../gcc-3.4.3/boehm-gc/mark.c:1468
> 
> Which shows that your crash is in the garbage collector, and therefore
> nothing to do with this old bug report.

Ok, I guess that verifies I did the right thing by filing a new one.  Thanks.

-Nathan


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5487


      parent reply	other threads:[~2005-09-01 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020125014600.5487.jsantala@tml.hut.fi>
2005-08-26 18:19 ` ngmlinux at gmail dot com
2005-08-31 20:34 ` ngmlinux at gmail dot com
2005-09-01 10:19 ` rearnsha at gcc dot gnu dot org
2005-09-01 19:52 ` ngmlinux at gmail dot com [this message]

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=20050901195204.29579.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).