Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: recognize 64 bits Windows executables as Cygwin osabi
Date: Tue, 10 Mar 2020 17:16:12 +0200	[thread overview]
Message-ID: <83pndk9r5v.fsf@gnu.org> (raw)
In-Reply-To: <85cd5fc2-8fa7-3612-b974-b3a3261bbb29@dronecode.org.uk> (message from Jon Turney on Sun, 8 Mar 2020 14:05:10 +0000)

> 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.

> (currently 'print sizeof(long)' incorrectly returns 4 on a gdb built for 
> Cygwin)

So I guess calling it "Cygwin" doesn't help? ;-)


  reply	other threads:[~2020-03-10 15:16 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 [this message]
2020-03-10 15:45           ` Simon Marchi
2020-03-14 15:35             ` Jon Turney
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=83pndk9r5v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jon.turney@dronecode.org.uk \
    /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