From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
Date: Mon, 11 Apr 2016 19:55:00 -0000 [thread overview]
Message-ID: <20160411195537.GA22299@host1.jankratochvil.net> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B23332A7343@IRSMSX104.ger.corp.intel.com>
Hello Markus,
On Mon, 11 Apr 2016 08:44:23 +0200, Metzger, Markus T wrote:
> > From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> > owner@sourceware.org] 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
testsuite.
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:
https://sourceware.org/ml/gdb-patches/2010-07/msg00343.html
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.
Thanks,
Jan
next prev parent reply other threads:[~2016-04-11 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:53 Jan Kratochvil
2016-04-11 6:44 ` Metzger, Markus T
2016-04-11 19:55 ` Jan Kratochvil [this message]
2016-07-20 14:02 ` Pedro Alves
2016-07-20 14:22 ` [commit] " Jan Kratochvil
2016-07-20 14:26 ` Metzger, Markus T
2016-07-20 14:32 ` Jan Kratochvil
2016-07-20 14:36 ` Pedro Alves
2016-07-20 14:39 ` Jan Kratochvil
2016-07-20 15:07 ` Pedro Alves
2016-07-21 13:51 ` Metzger, Markus T
2016-07-21 14:00 ` Pedro Alves
2016-07-21 14:06 ` Metzger, Markus T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160411195537.GA22299@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox