Re: [pushed] [gdb/testsuite] Add and use is_x86_64_m64_target

[Tom de Vries <tdevries@suse.de>]

On 1/26/23 17:38, Pedro Alves wrote:
> On 2023-01-26 4:10 p.m., Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>>
>> Tom> On 1/26/23 10:17, Tom de Vries wrote:
>>>> ./gdb.base/jit-reader.exp:
>>>>    require {is_any_target "i?86-*-*" "x86_64-*-*"} is_lp64_target
>>>> ./gdb.arch/amd64-i386-address.exp:
>>>>    require {is_any_target "x86_64-*-*" "i?86-*-*"} is_lp64_target
>>
>> Tom> And, doesn't is_lp64_target imply that we're not on an "i?86-*-*" ?
>>
>> Tom> Am I missing something here?
>>
>> I am not sure.  Can you use 'gcc -m64' on an x86?
> 
> Yeah, you can.  CodeSourcery toolchains used to be like that back in the day -- 32-bit
> hosted, so the target triplet indicated 32-bit, but you could use -m64 for 64-bit.
> No clue what they do nowadays.

Ah, that's interesting, thanks.

So, perhaps then you could indeed end up with is_lp64_target == true on 
an i?86 (by using target board unix/-m64).

But assuming you would end up with a complete 64-bit executable, you 
still wouldn't been able to run it on the 32-bit target, so I think it's 
a corner-case that doesn't prevent us from dropping the i?86 test here.

Thanks,
- Tom

> 
> Pedro Alves
> 
>> Or could you have a
>> 64-bit machine that advertises as i386 if userspace is mostly 32-bit?
> 
>