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 14:06:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23332F77B3@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <759c4b90-219f-deb5-495f-9fc3c978f890@redhat.com>

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Thursday, July 21, 2016 4:00 PM
> To: Metzger, Markus T <markus.t.metzger@intel.com>; Jan Kratochvil
> <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: [commit] [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on
> x86_64-m32
> 
> On 07/21/2016 02:50 PM, Metzger, Markus T wrote:
> 
> > 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.
> 
> But that's exactly what you want.
> 
> >
> > Is there a recommended/documented way on how this should be done?
> 
> - is_amd64_regs_target detects x86_64 ISA.
> 
> - is_lp64_target detects 64-bit/32-bit pointers.
> 
> Thus:
> 
>   is_amd64_regs_target && is_lp64_target  == 64-bit
>   is_amd64_regs_target && !is_lp64_target == x32
>   !is_amd64_regs_target                   == 32-bit
> 
> See intro comments to is_amd64_regs_target and proc is_x86_like_target.

Thanks,  looks like just "is_amd64_regs_target" is what I want.

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 14:06 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
2016-07-21 14:00                 ` Pedro Alves
2016-07-21 14:06                   ` Metzger, Markus T [this message]

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=A78C989F6D9628469189715575E55B23332F77B3@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