[PATCH 2/4] bfd|gas|ld: add i386-phoenix target
Michal Lach
michal.lach@phoenix-rtos.com
Tue Mar 10 13:07:09 GMT 2026
Jan Beulich <jbeulich@suse.com> writes:
> On 05.03.2026 19:04, Michał Lach wrote:
>> --- a/bfd/config.bfd
>> +++ b/bfd/config.bfd
>> @@ -785,6 +785,10 @@ case "${targ}" in
>> targ_defvec=i386_elf32_vxworks_vec
>> targ_underscore=yes
>> ;;
>> + i[3-7]86-*-phoenix*)
>
> Yes, other entries use 3-7, but can we please stop this for new entries?
> There never was an i786.
>
>> + targ_defvec=i386_elf32_vec
>> + targ_selvecs=
>
> No need for this when nothing needs adding.
>
Will address both these issues in v2.
>> --- a/ld/configure.tgt
>> +++ b/ld/configure.tgt
>> @@ -431,6 +431,9 @@ i[3-7]86-*-haiku*) targ_emul=elf_i386_haiku
>> ;;
>> i[3-7]86-*-vxworks*) targ_emul=elf_i386_vxworks
>> ;;
>> +i[3-7]86-*-phoenix*) targ_emul=elf_i386_phoenix
>> + targ_extra_emuls=elf_i386
>
> How are the two targets distinguished, when in bfd/config.bfd you use
> targ_defvec=i386_elf32_vec in the new entry?
Oh, right. elf_i386_phoenix just sources elf_i386 so we can just use
elf_i386 as targeted emulation?
Also, this applies to the SPARC patch too?
More information about the Binutils
mailing list