From: Richard Earnshaw <rearnsha@arm.com>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: SIM: Handle XScale COFF binaries
Date: Tue, 05 Feb 2002 03:05:00 -0000 [thread overview]
Message-ID: <200202051104.LAA02467@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "05 Feb 2002 10:55:56 GMT." <m3elk0fb9f.fsf@north-pole.nickc.cambridge.redhat.com>
> Hi Guys,
>
> I have checked in the following patch. It fixes the ARM simulator
> so that COFF based XScale binaries will be correctly simulated. The
> problem was that the COFF header did not have enough bits to
> distinguish between the v5, v5T, v5TE and XScale architectures, and
> so it was defaulting to v5, disabling the simulation of the XScale
> instructions.
>
> Cheers
> Nick
>
> 2002-02-04 Nick Clifton <nickc@cambridge.redhat.com>
>
> * wrapper.c: If a v5 architecture is detected, assume it might be
> an XScale binary, since there is no way to distinguish between
> the two in the COFF file format.
UG.
Can't we restrict this so that it only happens if we have COFF files (as
it stands ELF files will do the same as well).
R.
prev parent reply other threads:[~2002-02-05 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 2:55 Nick Clifton
2002-02-05 3:05 ` Richard Earnshaw [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=200202051104.LAA02467@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@cambridge.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