From: Jon Turney <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH] gdb: recognize 64 bits Windows executables as Cygwin osabi
Date: Sat, 14 Mar 2020 15:35:23 +0000 [thread overview]
Message-ID: <099967c9-ee83-63f5-fa41-98ca5de1c7de@dronecode.org.uk> (raw)
In-Reply-To: <97ad4d74-4c9b-8630-f573-ca6d476dfe21@simark.ca>
On 10/03/2020 15:45, Simon Marchi wrote:
> On 2020-03-10 11:16 a.m., Eli Zaretskii wrote:
>>> From: Jon Turney <jon.turney@dronecode.org.uk>
>>> Date: Sun, 8 Mar 2020 14:05:10 +0000
>>>
>>>>> So what we can do is add an "MS-Windows" osabi and make "Cygwin" and
>>>>> "MS-Windows" functionally equivalent. Any "pei-i386" or "pei-x86-64"
>>>>> executable would be detected as "MS-Windows".
>>>
>>> I believe this suggestion for x86_64 is wrong, in the other direction:
>>> x86_64 Cygwin is LP64, but Windows is LLP64 (Se also table in [1])
>>
>> If the LP64 thing is part of what defines the OS ABI, then yes, Cygwin
>> should have a separate value.
>
> If I understand correctly, that's one practical reason for introducing the separate
> "Windows" OS ABI?
That's the suggestion in:
https://sourceware.org/bugzilla/show_bug.cgi?id=21500
next prev parent reply other threads:[~2020-03-14 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200307041742.31158-1-simon.marchi@efficios.com>
[not found] ` <83zhcsa8my.fsf@gnu.org>
2020-03-07 16:51 ` Simon Marchi
2020-03-07 17:45 ` Eli Zaretskii
2020-03-07 18:16 ` Simon Marchi
2020-03-08 14:05 ` Jon Turney
2020-03-10 15:16 ` Eli Zaretskii
2020-03-10 15:45 ` Simon Marchi
2020-03-14 15:35 ` Jon Turney [this message]
2020-03-09 15:39 ` Jon Turney
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=099967c9-ee83-63f5-fa41-98ca5de1c7de@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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