From: Nick Clifton <nickc@cambridge.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: SIM: Handle XScale COFF binaries
Date: Tue, 05 Feb 2002 02:55:00 -0000 [thread overview]
Message-ID: <m3elk0fb9f.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
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.
Index: sim/arm/wrapper.c
===================================================================
RCS file: /cvs/src/src/sim/arm/wrapper.c,v
retrieving revision 1.15
retrieving revision 1.16
diff -c -3 -p -w -r1.15 -r1.16
*** wrapper.c 2002/01/09 15:08:21 1.15
--- wrapper.c 2002/02/04 16:27:22 1.16
*************** sim_create_inferior (sd, abfd, argv, env
*** 234,239 ****
--- 234,248 ----
break;
case bfd_mach_arm_5:
+ /* This is a special case in order to support COFF based ARM toolchains.
+ The COFF header does not have enough room to store all the different
+ kinds of ARM cpu, so the XScale, v5T and v5TE architectures all default
+ to v5. (See coff_set_flags() in bdf/coffcode.h). So if we see a v5
+ machine type here, we assume it could be any of the above architectures
+ and so select the most feature-full. */
+ ARMul_SelectProcessor (state, ARM_v5_Prop | ARM_v5e_Prop | ARM_XScale_Prop);
+ break;
+
case bfd_mach_arm_5T:
ARMul_SelectProcessor (state, ARM_v5_Prop);
break;
next reply other threads:[~2002-02-05 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 2:55 Nick Clifton [this message]
2002-02-05 3:05 ` Richard Earnshaw
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=m3elk0fb9f.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=gdb-patches@sources.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