From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
"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 06:44:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23332A7343@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20160408155331.GA31979@host1.jankratochvil.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
next prev parent reply other threads:[~2016-04-11 6:44 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 [this message]
2016-04-11 19:55 ` Jan Kratochvil
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=A78C989F6D9628469189715575E55B23332A7343@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).