From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Thu, 11 Feb 2016 22:50:39 +0200 [thread overview]
Message-ID: <83wpqb7yzk.fsf@gnu.org> (raw)
In-Reply-To: <jwvsi0zpd4p.fsf-monnier+gmane.emacs.help@gnu.org> (message from Stefan Monnier on Thu, 11 Feb 2016 08:58:45 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 11 Feb 2016 08:58:45 -0500
>
> >> Could I ask, what is the benefit of 64 bits compared to 32 bits for windows ?
> > It will run roughly twice faster.
> [...]
> > slower, because running a 32-bit executable on a 64-bit Windows
> > requires expensive thunking for every call to any Windows API,
>
> Holy crap? Really? It's hard to believe that 64-bit Windows's
> emulation of the 32-bit API is so inefficient that it causes a "rough
> slowdown" by a factor 2 in an application like Emacs.
>
> Do you see such a factor-of-2 difference when doing "rm lisp/**/*.elc;
> make"? Or in which kind of circumstance have you seen such a slowdown?
I measured that by running GNU Find compiled from the same sources on
a large and deep directory tree on the same Windows 7 box.
That thunking is the culprit is my theory, not a fact; however, I
cannot find any other explanation. If someone does, I'm all ears.
next prev parent reply other threads:[~2016-02-11 20:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 23:01 64 bit official Windows builds Sam Halliday
2015-12-25 7:35 ` Eli Zaretskii
2015-12-25 13:35 ` Óscar Fuentes
2015-12-25 14:21 ` Eli Zaretskii
2015-12-25 15:32 ` Random832
2015-12-25 15:52 ` Eli Zaretskii
2016-01-07 22:47 ` Arash Esbati
2016-01-08 9:12 ` Eli Zaretskii
2016-01-08 21:42 ` Arash Esbati
2016-01-09 6:58 ` Eli Zaretskii
[not found] ` <mailman.1936.1452244338.843.help-gnu-emacs@gnu.org>
2016-01-08 10:44 ` Sam Halliday
2016-01-08 11:09 ` Eli Zaretskii
[not found] ` <mailman.1913.1452206888.843.help-gnu-emacs@gnu.org>
2016-01-09 13:04 ` Sam Halliday
2016-01-10 21:19 ` Arash Esbati
2016-02-11 21:21 ` Nicolas Petton
2016-02-11 21:35 ` Kaushal Modi
2016-02-11 21:53 ` John Mastro
[not found] ` <mailman.556.1451028922.843.help-gnu-emacs@gnu.org>
2016-01-07 22:38 ` Sam Halliday
2016-01-07 23:15 ` Rasmus
2016-01-08 9:05 ` Eli Zaretskii
2016-02-08 17:44 ` moocow062
2016-02-08 18:06 ` Eli Zaretskii
2016-02-08 18:29 ` Óscar Fuentes
2016-02-08 19:10 ` Eli Zaretskii
2016-02-11 13:58 ` Stefan Monnier
2016-02-11 20:50 ` Eli Zaretskii [this message]
2016-02-11 22:16 ` Óscar Fuentes
2016-02-12 6:55 ` Eli Zaretskii
2016-02-12 7:16 ` Óscar Fuentes
2016-02-12 7:48 ` Eli Zaretskii
2016-02-12 8:16 ` Óscar Fuentes
2016-02-12 8:51 ` Eli Zaretskii
2016-02-08 22:13 ` djc
2016-02-08 22:51 ` Óscar Fuentes
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=83wpqb7yzk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).