This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix register selection in var-access.exp
- From: Pedro Alves <palves at redhat dot com>
- To: Simon Marchi <simon dot marchi at polymtl dot ca>, Andreas Arnez <arnez at linux dot vnet dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 13 Jun 2017 22:24:27 +0100
- Subject: Re: [PATCH] Fix register selection in var-access.exp
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=palves at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 15DF880495
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 15DF880495
- References: <m3a85b3fej.fsf@oc1027705133.ibm.com> <0dc97ea8ffe3b55b2a114ba1102f23c0@polymtl.ca>
On 06/13/2017 09:33 PM, Simon Marchi wrote:
> However could you (or somebody else) explain this to me? The doc of
> is_amd64_regs_target says:
>
> 2465 # Return 1 if target has x86_64 registers - either amd64 or x32.
> 2466 # x32 target identifies as x86_64-*-linux*, therefore it cannot be
> determined
> 2467 # just from the target string.
>
> If x32 identifies as x86_64-something and that procedure should return
> true when testing with x32 and x86_64/amd64, why can't we test the
> target string for x86_64-*?
Some vendors build --target i686-* toolchains, and then
use -m64 to target the 64-bit multilib.
Thanks,
Pedro Alves