darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Modify previous patch so that it is only triggered for COFF format executables.

Browse source
This commit is contained in:
Nick Clifton 2002-02-05 11:22:26 +00:00
parent 82f6addb56
commit c17aa31873
2 changed files with 20 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
sim/arm/ChangeLog
View file

@ -1,8 +1,13 @@
2002-02-05 Nick Clifton <nickc@cambridge.redhat.com>
* wrapper.c (sim_create_inferior): Modify previous patch so that
it is only triggered for COFF format executables.
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.
* wrapper.c (sin_create_inferior): 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.
2002-01-10 Nick Clifton <nickc@cambridge.redhat.com>

20
sim/arm/wrapper.c
View file

@ -234,14 +234,18 @@ sim_create_inferior (sd, abfd, argv, env)
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;
if (bfd_family_coff (abfd))
{
/* 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;
}
/* Otherwise drop through. */
case bfd_mach_arm_5T:
ARMul_SelectProcessor (state, ARM_v5_Prop);