From: Eli Zaretskii <eliz@gnu.org>
To: oscarfv@telefonica.net (Óscar Fuentes)
Cc: 18699@debbugs.gnu.org
Subject: bug#18699: 25.0.50; Windows 7: Odd length text property list
Date: Mon, 13 Oct 2014 15:49:13 +0300 [thread overview]
Message-ID: <83k3446som.fsf@gnu.org> (raw)
In-Reply-To: <8761fojiml.fsf@telefonica.net>
> From: oscarfv@telefonica.net (Óscar Fuentes)
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 13 Oct 2014 13:46:22 +0200
>
> The MinGW-w64 guys say that _W64 is not the rigth way of checking that
> we are targeting Windows 64. _WIN64 is.
I'm quite sure at some point someone told me the exact opposite of
this, whcih is why you see what you see in nt/inc/.
> The right way to detect MinGW-w64 is to test for __MINGW64_VERSION_MAJOR
> *after* including some C runtime header or _mingw.h, because it is not a
> preprocessor predefined macro.
It is a PITA that the MinGW64 compiler doesn't define some clear-cut
macro for that without the need to include headers. IME this is a
terrible maintenance headache in the long run. Perhaps you could ask
the MinGW64 developers to change their mind about that.
What about __x86_64__, does it perhaps fit the bill already?
> Eli, can you take care of the ALIGN_STACK fix?
Done in trunk revision 118105.
> I'll send a patch for the rest of _W64 cases, if nobody beats me to
> it.
TIA
next prev parent reply other threads:[~2014-10-13 12:49 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 [this message]
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
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=83k3446som.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18699@debbugs.gnu.org \
--cc=oscarfv@telefonica.net \
/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).