From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: MS-Windows tester wanted for trunk
Date: Tue, 16 Sep 2014 19:03:22 +0300 [thread overview]
Message-ID: <83a95z4kol.fsf@gnu.org> (raw)
In-Reply-To: <54185B53.7030900@yandex.ru>
> Date: Tue, 16 Sep 2014 19:46:27 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: emacs-devel@gnu.org
>
> On 09/16/2014 06:31 PM, Eli Zaretskii wrote:
>
> > So, as suggested by that page, I marked the callback functions in
> > w32font.c with '__attribute__((force_align_arg_pointer))', and then
> > Emacs comes up normally. This attribute is available in GCC since
> > v4.2.
>
> From GCC manual, as of 4.8:
>
> -mstackrealign
>
> Realign the stack at entry.
That's the other solution suggested by the URL I cited. But it's too
expensive: it adds the realignment overhead to _every_ function call.
By contrast, the number of callback functions we have is quite small,
and even if we decorate all of them with force_align_arg_pointer
(which isn't strictly necessary, AFAIU, since most of them don't cons
Lisp data), that's just a handful of functions that are not
performance-critical.
Is it possible to prevent this problem by using an intermediate local
variable with a suitable alignment (sorry if this is a silly question,
but I have only a very vague idea about alignment).
next prev parent reply other threads:[~2014-09-16 16:03 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
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 [this message]
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=83a95z4kol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--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).