From: oscarfv@telefonica.net (Óscar Fuentes)
To: Ken Brown <kbrown@cornell.edu>
Cc: 18699@debbugs.gnu.org
Subject: bug#18699: 25.0.50; Windows 7: Odd length text property list
Date: Mon, 13 Oct 2014 21:39:33 +0200 [thread overview]
Message-ID: <87wq83iwsq.fsf@wanadoo.es> (raw)
In-Reply-To: <543C24AD.7090101@cornell.edu> (Ken Brown's message of "Mon, 13 Oct 2014 15:14:53 -0400")
Ken Brown <kbrown@cornell.edu> writes:
> Right. And it's *not* about the processor. gcc running under 32-bit
> Cygwin will not define __x86_64__, regardless of the processor.
It is about the *target* processor of the compiler. Obviously if you
target x86 then __x86_64__ is expected to be undefined, regardless of
the *host* processor.
OTOH if you are saying that Cygwin does not define __x86_64__ when you
are cross-compiling to a x86_64 target on a x86 host, I'll consider that
a bug.
My understanding now is that the __x86_64__ test is there because Cygwin
does not define _WIN64.
Eli, both MinGW and MinGW-w64 compilers support sjlj and Dwarf exception
methods on x86. Maybe MinGW only supports one method on its official
binaries, but that's just a detail that can change at any moment. Plus
the user can build his own toolchain. And since when we do care about
C++ here? ;-)
next prev parent reply other threads:[~2014-10-13 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 0:58 bug#18699: 25.0.50; Windows 7: Odd length text property list Óscar Fuentes
[not found] ` <handler.18699.B.141316196215131.ack@debbugs.gnu.org>
2014-10-13 2:02 ` Óscar Fuentes
2014-10-13 5:31 ` Eli Zaretskii
2014-10-13 6:14 ` Eli Zaretskii
2014-10-13 10:27 ` Óscar Fuentes
2014-10-13 11:37 ` Eli Zaretskii
2014-10-13 11:46 ` Óscar Fuentes
2014-10-13 12:49 ` Eli Zaretskii
2014-10-13 13:57 ` Óscar Fuentes
2014-10-13 19:07 ` Eli Zaretskii
2014-10-13 19:14 ` Ken Brown
2014-10-13 19:39 ` Óscar Fuentes [this message]
2014-10-13 20:25 ` Eli Zaretskii
2014-10-13 20:35 ` Óscar Fuentes
2014-10-14 6:09 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wq83iwsq.fsf@wanadoo.es \
--to=oscarfv@telefonica.net \
--cc=18699@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).