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: Tue, 14 Oct 2014 09:09:31 +0300 [thread overview]
Message-ID: <83bnpf6v38.fsf@gnu.org> (raw)
In-Reply-To: <87siiriu72.fsf@wanadoo.es>
> From: oscarfv@telefonica.net (Óscar Fuentes)
> Cc: kbrown@cornell.edu, 18699@debbugs.gnu.org
> Date: Mon, 13 Oct 2014 22:35:45 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > A 64-bit build on Windows, whether a Cygwin build or a MinGW64 build,
> > doesn't need the force_align_arg_pointer, since the 64-bit ABI
> > requires the 8-byte alignment. The __x86_64__ is there to exclude the
> > 64-bit Cygwin build. If it can also exclude the MinGW64 build, we
> > don't need any MinGW64-specific symbols there.
>
> As mentioned on a previous message, __x86_64__ will exclude Windows 64
> on x86* processors, but not on others (i.e. ARM).
We could decide not to worry about that until we need to support a
Windows build on any of those others. Like we do with Cygwin.
prev parent reply other threads:[~2014-10-14 6:09 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
2014-10-13 20:25 ` Eli Zaretskii
2014-10-13 20:35 ` Óscar Fuentes
2014-10-14 6:09 ` Eli Zaretskii [this message]
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=83bnpf6v38.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).