public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jay <jayk123@hotmail.com>
To: <tromey@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: gcj/sparc64?
Date: Fri, 25 Jul 2008 07:01:00 -0000	[thread overview]
Message-ID: <COL101-W684585AE20487F7355EF4BE6860@phx.gbl> (raw)
In-Reply-To: <m3k5fbl4ly.fsf@fleche.redhat.com>


Sorry Tom, I find opening bugs often tedious..sign up an account, fill in a bunch of fields..
I'll try to get more details "later" (if it repros consistently, callstack in a debugger) 
 
 - Jay

> To: Jayk 
> CC: gcc 
> Subject: Re: gcj/sparc64? 
> From: Tom  
> Date: Thu, 24 Jul 2008 08:49:13 -0600 
> 
>>>>>> Jay writes:
> 
> Jay> This is an incomplete bug report.
> Jay> unified gcc 4.3.1/binutils 2.18/gmp/mpfr tree: 
> Jay> -bash-3.00$ gcc -v 
> Jay> Using built-in specs. 
> Jay> Target: sparc-sun-solaris2.10 
> 
> [...]
> Jay> /.libs/HTML_401F.o 
> Jay> gcj: Internal error: Segmentation Fault (program jc1) 
> Jay> Please submit a full bug report. 
> 
> Knowing this particular file, maybe gcj just ran out of memory.
> Anyway, please file in bugzilla. If you can include a jc1 stack
> trace, that would be helpful.

  reply	other threads:[~2008-07-25  5:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1216680495.31069.ezmlm@gcc.gnu.org>
2008-07-24 10:01 ` gcj/sparc64? Jay
2008-07-24 15:11   ` gcj/sparc64? Tom Tromey
2008-07-25  7:01     ` Jay [this message]
2008-07-26 17:55     ` gcj/sparc64? Andrew Haley
2008-08-10  8:49       ` gcj/sparc64? Jay
2008-08-10 13:42         ` gcj/sparc64? Brian Dessent
2008-08-10 14:37           ` gcj/sparc64? Jay
2008-08-10 22:57             ` gcj/sparc64? Andreas Schwab
2008-08-11 13:19           ` gcj/sparc64? Jay

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=COL101-W684585AE20487F7355EF4BE6860@phx.gbl \
    --to=jayk123@hotmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=tromey@redhat.com \
    /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).