From: Tim Prince <tprince@computer.org>
To: Jim Wilson <wilson@redhat.com>
Cc: Aldy Hernandez <aldyh@redhat.com>, gcc@gcc.gnu.org
Subject: Re: ia64 linux doesn't bootstrap
Date: Sat, 19 Oct 2002 07:39:00 -0000 [thread overview]
Message-ID: <20021019060719.5087A2CB25@inet1.ywave.com> (raw)
In-Reply-To: <xwuof9r67b2.fsf@tonopah.toronto.redhat.com>
On Friday 18 October 2002 09:27, Jim Wilson wrote:
> >Maybe OT, but what version of gdb would you use, and which version of gcc
> >would you build it with?
>
> /usr/bin/gdb and /usr/bin/gcc. Maybe I didn't understand the question?
>
I was unaware of the sourceforge gdbf95 project, which provides a more
functional gdb than I had seen before. I've tried to build gdb-5.2.1 with
gcc-3.3, and it failed with many complaints about illegal code. It did
succeed with a buggy pre-3.0 gcc; there were I think 254 unexpected errors in
testsuite. Maybe that's acceptable? Anyway, I hope to be able soon to
whittle down a test case for the current breakage in gcc -funroll-loops, now
that I have a gdb which is able to step through code.
--
Tim Prince
next prev parent reply other threads:[~2002-10-19 6:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 4:53 Aldy Hernandez
2002-10-18 7:33 ` Tim Prince
2002-10-18 11:49 ` Jim Wilson
2002-10-19 7:39 ` Tim Prince [this message]
2002-10-22 15:23 ` Jim Wilson
2002-10-24 4:43 ` tprinceusa
2002-10-18 8:18 ` Andreas Schwab
2002-10-18 12:49 ` Janis Johnson
2002-10-18 12:53 ` David Edelsohn
2002-10-18 16:05 ` David Edelsohn
2002-10-18 17:04 ` Mark Mitchell
2002-10-18 17:12 ` Janis Johnson
2002-10-19 1:09 ` David Edelsohn
2002-10-21 3:28 ` Mark Mitchell
2002-10-21 18:03 ` Jim Wilson
2002-10-21 19:49 ` Janis Johnson
2002-10-20 6:16 ` Andreas Schwab
2002-10-20 9:43 ` Janis Johnson
2002-10-18 13:01 ` Aldy Hernandez
2002-10-21 20:34 Ulrich Weigand
2002-10-21 23:35 ` David Edelsohn
2002-10-22 10:43 ` Ulrich Weigand
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=20021019060719.5087A2CB25@inet1.ywave.com \
--to=tprince@computer.org \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=wilson@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).