This is the mail archive of the
mailing list for the GDB project.
Re: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 11 Apr 2016 21:55:37 +0200
- 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> <A78C989F6D9628469189715575E55B23332A7343 at IRSMSX104 dot ger dot corp dot intel dot com>
On Mon, 11 Apr 2016 08:44:23 +0200, Metzger, Markus T wrote:
> > From: firstname.lastname@example.org [mailto:gdb-patches-
> > email@example.com] On Behalf Of Jan Kratochvil
> > $ runtest 'CC_FOR_TARGET=gcc -m32' gdb.btrace/tailcall-only.exp Running
> 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"
that is an interesting idea and I agree it is a more correct way to run the
Nonetheless it seems to me GDB does not require arch-specific target_triplet
to be set, I have searched now a bit and picked for example:
This is why the functions like is_lp64_target were created.
I will leave it up to the GDB maintainers what is the correct way and possibly
adjust my testing scripts accordingly.