Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>,
	Jan Kratochvil	<jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [commit] [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
Date: Thu, 21 Jul 2016 13:51:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23332F7778@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <2234b2b7-47af-9887-ee70-495be177f038@redhat.com>

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Wednesday, July 20, 2016 5:08 PM
> To: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Metzger, Markus T <markus.t.metzger@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [commit] [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on
> x86_64-m32
> 
> On 07/20/2016 03:38 PM, Jan Kratochvil wrote:
> > On Wed, 20 Jul 2016 16:36:46 +0200, Pedro Alves wrote:
> >> Not sure this particular commit, but AFAIK, there's no target
> >> triplet for x32, even.
> >
> > https://sourceware.org/glibc/wiki/x32
> > ->
> > x86_64-x32-linux
> 
> AFAICS, that "x32" is in the "vendor" part of the triplet, which should
> never mean anything for the tools themselves, being a free field to use by
> whoever builds the tools, in order to give the binaries a unique
> file name (x86_64-x32-linux-gcc, etc.), and for branding, like
> x86_64-redhat-linux-gcc.  AFAICS, nothing in config.sub, and the
> different configure scripts in binutils-gdb select on *-x32-*.
> 
> ISTR that a triplet like x86_64-*-linux-gnux32 or x86_64-*-linux-gnu-x32
> was originally proposed, but then the toolchain ended using strictly
> multilib flags to select/detect x32.  But, actually, now that I grep, I find
> a few hits on "x86_64-*-linux-gnux32", though not many, so it looks like
> there's a triplet after all.

I use the triplet to select the source files for a test.  Seems that wasn't such
a good idea.

Using the pointer size doesn't seem to be such a good idea, either, as x32
uses x86_64 ISA with 32-bit pointers.

Is there a recommended/documented way on how this should be done?


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


  reply	other threads:[~2016-07-21 13:51 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
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 [this message]
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=A78C989F6D9628469189715575E55B23332F7778@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@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