From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] [gdb/testsuite] Add and use is_x86_64_m64_target
Date: Thu, 26 Jan 2023 17:36:36 +0100 [thread overview]
Message-ID: <e4ce8142-b72e-e5d3-d5d4-f183d3ba33a3@suse.de> (raw)
In-Reply-To: <87fsbxs2dn.fsf@tromey.com>
On 1/26/23 17:10, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Tom> On 1/26/23 10:17, Tom de Vries wrote:
>>> ./gdb.base/jit-reader.exp:
>>> require {is_any_target "i?86-*-*" "x86_64-*-*"} is_lp64_target
>>> ./gdb.arch/amd64-i386-address.exp:
>>> require {is_any_target "x86_64-*-*" "i?86-*-*"} is_lp64_target
>
> Tom> And, doesn't is_lp64_target imply that we're not on an "i?86-*-*" ?
>
> Tom> Am I missing something here?
>
> I am not sure. Can you use 'gcc -m64' on an x86?
AFAIK, no.
> Or could you have a
> 64-bit machine that advertises as i386 if userspace is mostly 32-bit?
I think that could be, but AFAIU, is_lp64_target would be false for such
a setup.
Thanks,
- Tom
next prev parent reply other threads:[~2023-01-26 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:06 [RFC 0/3] [gdb/testsuite] Introduce is_x86_64_m64_target Tom de Vries
2023-01-25 20:06 ` [RFC 1/3] [gdb/contrib] Add refactor.py Tom de Vries
2023-01-25 20:06 ` [RFC 2/3] [gdb/contrib] Add refactor_require.py Tom de Vries
2023-01-25 20:06 ` [RFC 3/3] [gdb/testsuite] Add and use is_x86_64_m64_target Tom de Vries
2023-01-25 21:25 ` Tom Tromey
2023-01-26 9:17 ` [pushed] " Tom de Vries
2023-01-26 15:48 ` Tom de Vries
2023-01-26 16:10 ` Tom Tromey
2023-01-26 16:36 ` Tom de Vries [this message]
2023-01-26 16:38 ` Pedro Alves
2023-01-26 17:08 ` Tom de Vries
2023-01-26 18:25 ` Tom Tromey
2023-01-26 18:34 ` Pedro Alves
2023-01-25 21:26 ` [RFC 0/3] [gdb/testsuite] Introduce is_x86_64_m64_target Tom Tromey
2023-01-26 9:30 ` Tom de Vries
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=e4ce8142-b72e-e5d3-d5d4-f183d3ba33a3@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).