From: Dmitry Antipov <dmantipov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MS-Windows tester wanted for trunk
Date: Tue, 16 Sep 2014 19:24:28 +0400 [thread overview]
Message-ID: <5418562C.9040501@yandex.ru> (raw)
In-Reply-To: <83r3zb4oyh.fsf@gnu.org>
On 09/16/2014 06:31 PM, Eli Zaretskii wrote:
> So the conclusion is that, at least for 32-bit Windows builds, the
> alignment of union Aligned_Cons is not enough to produce the effect
> you want, and additional measures are necessary.
>
> I don't expect this to be a problem in 64-bit Windows builds, because
> there Windows does enforce 16-byte alignment of the stack. But, as I
> already said, I didn't test that.
Do we have the same issue with alloca? If not, whether it will be
simpler to define scoped_cons to local_cons for 32-bit Windows builds?
> This could be an issue in other x86 32-bit builds (probably not on
> GNU/Linux, though, and not if GCC is the compiler), because AFAIK the
> x86 ABI specifies a 4-byte stack alignment.
Hm...I'll try 32-bit builds with clang and icc. BTW, both of them mimics
GCC quite well, so I will be very surprised with an issues here.
Dmitry
next prev parent reply other threads:[~2014-09-16 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 8:50 MS-Windows tester wanted for trunk Dmitry Antipov
2014-09-16 13:10 ` Chris Zheng
2014-09-16 14:48 ` Eli Zaretskii
2014-09-16 14:54 ` Chris Zheng
2014-09-16 14:56 ` Chris Zheng
2014-09-16 15:10 ` Eli Zaretskii
2014-09-17 9:28 ` Chris Zheng
2014-09-17 10:03 ` Eli Zaretskii
2014-09-17 16:56 ` Clang ? [Was: Re: MS-Windows tester wanted for trunk] Dmitry Antipov
2014-09-18 1:05 ` Paul Eggert
2014-09-24 14:45 ` Dmitry Antipov
2014-09-16 14:31 ` MS-Windows tester wanted for trunk Eli Zaretskii
2014-09-16 15:24 ` Dmitry Antipov [this message]
2014-09-16 15:58 ` Eli Zaretskii
2014-09-16 20:40 ` Ken Brown
2014-09-16 15:46 ` Dmitry Antipov
2014-09-16 16:03 ` Eli Zaretskii
2014-09-16 14:38 ` 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=5418562C.9040501@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).