From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Fri, 12 Feb 2016 08:16:37 +0100 [thread overview]
Message-ID: <87vb5us8iy.fsf@wanadoo.es> (raw)
In-Reply-To: 83h9he8lkp.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> > 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.
>>
>> I mentioned some possibilities on a previous message. Did you use the
>> same toolset and libraries for the 32 and 64 bits build?
>
> No. The program was compiled by mingw.org's MinGW for 32 bits and by
> MinGW64 for 64 bits.
There you have a strong candidate for explaining the difference. That
probably also means that they were different compiler versions.
>> The MinGW and MinGW-w64 (32/64 bits) runtimes diverged quite a bit.
>
> GNU Find uses only msvcrt.dll, no other runtime libraries are involved
> in any significant way.
As you know, there are other code pieces that are linked into the
executable besides the C runtime (which MinGW(-w64) supersede by
providing their implementations for certain functions, plus other
features missing from msvcrt.dll). IIRC some *stat functions are very
slow on Mingw, maybe the MinGW-w64 guys introduced improvements, just a
guess.
Why don't you build both 32 and 64 bits executables of GNU Find with
MinGW-w64 (same toolset version) for comparing its performance?
Not saying that GNU Find will be representative of what you can expect
from Emacs. (GNU Find: I/O bound; Emacs: user bound.)
next prev parent reply other threads:[~2016-02-12 7:16 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
2016-02-11 22:16 ` Óscar Fuentes
2016-02-12 6:55 ` Eli Zaretskii
2016-02-12 7:16 ` Óscar Fuentes [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb5us8iy.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.