This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32


On 04/11/2016 07:44 AM, Metzger, Markus T wrote:
>> -----Original Message-----
>> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
>> owner@sourceware.org] On Behalf Of Jan Kratochvil
>> Sent: Friday, April 8, 2016 5:54 PM
>> To: gdb-patches@sourceware.org
>> Cc: Metzger, Markus T <markus.t.metzger@intel.com>
>> Subject: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-
>> m32
> 
> Hi Jan,
> 
>> $ runtest 'CC_FOR_TARGET=gcc -m32' gdb.btrace/tailcall-only.exp Running
>> ./gdb.btrace/tailcall-only.exp ...
>> gdb compile failed, tailcall-only.c: Assembler messages:
>> tailcall-only.c:142: Error: cannot represent relocation type BFD_RELOC_64 [...]
>> tailcall-only.c:425: Error: cannot represent relocation type BFD_RELOC_64
> 
> I'm setting the target triplet to "i686-unknown-linux" in my m32 configuration.
> Like this:
> 
> set target_triplet "i686-unknown-linux"
> set_board_info cflags "-m32"
> set_board_info cppflags "-m32"
> 
> Should I rather not set the target_triplet?

There's no reason you should _not_ set it.

But, multilib-style testing with --target_board=unix\{-m64,-m32\} etc.
should work _too_, IMO.

Thanks,
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]