From: Richard Henderson <rth@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: egcs@egcs.cygnus.com, gdb@sourceware.cygnus.com
Subject: Re: IA32: printing FP register variables
Date: Mon, 19 Jul 1999 23:41:00 -0000 [thread overview]
Message-ID: <19990719234100.C17063@cygnus.com> (raw)
In-Reply-To: <npn1ws2xp1.fsf@zwingli.cygnus.com>
On Mon, Jul 19, 1999 at 03:26:18PM -0500, Jim Blandy wrote:
> Once the other internal work is done, would the EGCS folks be willing
> to experiment with both, and give us some sense of how much difference
> it makes?
Yes. It seems a reasonable thing to try.
r~
From tm@netcom.com Tue Jul 20 12:14:00 1999
From: Toshiyasu Morita <tm@netcom.com>
To: jtc@redback.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: GDB with Hitachi Linker output?
Date: Tue, 20 Jul 1999 12:14:00 -0000
Message-id: <199907201913.MAA22621@netcom13.netcom.com>
References: <5mwvvw74ic.fsf@jtc.redbacknetworks.com>
X-SW-Source: 1999-q3/msg00095.html
Content-length: 1478
The SRCONV utility is actually pretty broken, through no fault of Cygnus.
We ran into the problem three years ago that SRCONV-emitted files caused the
Hitachi in-circuit emulator to crash. After much consultation with both
sides, we determined that:
1) The Hitachi SYSROF spec only describes the output of the data from the
compiler/linker, and do not specify implicit ordering dependencies, and
2) linker/debugger are fragile and do not emit proper error messages
when a certain section is out of order.
Therefore, it was impossible to debug the problem and we gave up on SRCONV.
Toshi
>
> >>>>> "Bill" == Bill Gatliff <gatliff@haulpak.com> writes:
> Bill> Is anyone using GDB sh-hitachi-hms with executables supplied by
> Bill> the Hitachi linker?
>
> I don't think so.
>
> AFAIK, the hitachi object format is sysroff. There is a sysroff to
> COFF converter in binutils (srconv), but nothing to do the reverse. I
> vaguely remember a receiving email from Ian Taylor two or three years
> ago that said that support for whatever was missing in BFD that caused
> srconv to be a separate program (instead of available through objcopy)
> had been added. That project never became high enough priority to
> follow up.
>
> It's possible that the email was referring to nlmconv instead of
> srconv, since I worked on both programs in that time frame. I'm
> sorry I can't remember any more details.
>
> --jtc
>
> --
> J.T. Conklin
> RedBack Networks
>
next parent reply other threads:[~1999-07-19 23:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9500.931826533@upchuck.cygnus.com>
[not found] ` <np1zeci6tm.fsf@zwingli.cygnus.com>
[not found] ` <npn1ws2xp1.fsf@zwingli.cygnus.com>
1999-07-19 23:41 ` Richard Henderson [this message]
1999-07-26 11:43 ` Jim Blandy
1999-07-26 13:15 ` Richard Henderson
[not found] <400.931648196@upchuck.cygnus.com>
[not found] ` <np908ljwht.fsf@zwingli.cygnus.com>
[not found] ` <9209.931822541@upchuck.cygnus.com>
1999-07-12 16:50 ` Joern Rennecke
1999-07-12 17:18 ` Robert Lipe
1999-07-12 19:40 ` Richard Henderson
[not found] ` <np3dysi9gh.fsf@zwingli.cygnus.com>
1999-07-13 16:05 ` Richard Henderson
1999-07-09 14:00 Michael Meissner
[not found] <199907091724.SAA31114@phal.cygnus.co.uk>
[not found] ` <00d401beca31$3d752c10$3404010a@metrowerks.com>
1999-07-09 10:52 ` Jeffrey A Law
1999-07-09 13:50 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
1999-07-08 20:56 Jim Blandy
1999-07-08 22:12 ` Jeffrey A Law
[not found] ` <000d01bec9c2$06f4fdb0$3404010a@metrowerks.com>
1999-07-08 22:04 ` Jeffrey A Law
1999-07-09 7:04 ` Michael Meissner
1999-07-10 11:00 ` Tom Tromey
1999-07-09 10:53 ` Jim Blandy
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=19990719234100.C17063@cygnus.com \
--to=rth@cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jimb@cygnus.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