This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
- From: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 11 Apr 2016 06:44:23 +0000
- Subject: RE: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
- Authentication-results: sourceware.org; auth=none
- References: <20160408155331 dot GA31979 at host1 dot jankratochvil dot net>
> -----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?
In that case, there are a few more build errors in other gdb.btrace tests.
Thanks,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928