all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jostein@kjonigsen.net, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Regarding performance issues with the Emacs 25.1 Windows-build
Date: Wed, 9 Nov 2016 11:55:04 -0500	[thread overview]
Message-ID: <CAM-tV--vJmuSTEgQY=vnxSqOVy9mr6=UBd=H0VP7gTE8hg5A8Q@mail.gmail.com> (raw)
In-Reply-To: <83shr0fwsu.fsf@gnu.org>

On Wed, Nov 9, 2016 at 11:22 AM, Eli Zaretskii <eliz@gnu.org> wrote:

>> How was the Windows-version built? Was it built by the same people,
>> using the same setup and the same toolchain? Or was something done
>> differently this time?
>
> The answer is probably that it was not built the same, but I very much
> doubt that the differences could explain a twofold performance hit.
>
> FWIW, my binaries were built by myself using the same compilation
> options (-O2 optimization), but I upgraded my compiler from GCC 4.8.1
> to 5.3.0 between the two versions of Emacs.  Again, I very much doubt
> that this could explain any significant performance differences.

I think the problem is that the 25.1 build is not optimized: I did M-x
report-emacs-bug in each, notice that 25.1 has a setting for CFLAGS
which doesn't include -O2, while 24.5 doesn't have one (and hence uses
the default, which I believe does include -O2).

In GNU Emacs 25.1.1 (x86_64-w64-mingw32)
 of 2016-09-17 built on LAPHROAIG
Configured using:
 'configure --without-dbus --without-compress-install CFLAGS=-static'

In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.3.9600
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'



  reply	other threads:[~2016-11-09 16:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  8:34 Regarding performance issues with the Emacs 25.1 Windows-build Jostein Kjønigsen
2016-11-09 16:22 ` Eli Zaretskii
2016-11-09 16:55   ` Noam Postavsky [this message]
2016-11-09 17:18     ` Eli Zaretskii
2016-11-10 15:16       ` Phillip Lord
2016-11-10 22:04       ` Phillip Lord
2016-11-11  7:56         ` Eli Zaretskii
2016-11-11 20:53           ` Phillip Lord
2016-11-14 15:56             ` Phillip Lord
2016-11-14 16:19               ` Eli Zaretskii
2016-11-14 16:55                 ` Phillip Lord
2016-11-14 18:12                   ` Eli Zaretskii
2016-11-15 10:49                     ` Jostein Kjønigsen
2016-11-15 11:42                       ` Jostein Kjønigsen
2016-11-15 13:17                         ` Phillip Lord
2016-11-15 13:30                           ` Jostein Kjønigsen
2016-11-15 15:17                             ` Eli Zaretskii
2016-11-15 15:39                               ` Jostein Kjønigsen
2016-11-20  9:31                                 ` Phillip Lord
2016-11-29 18:26                                   ` Jostein Kjønigsen
2016-11-29 21:47                                     ` Phillip Lord
2016-11-30  7:56                                       ` Fabrice Popineau
2016-11-30  8:36                                         ` Jostein Kjønigsen
2016-11-30 12:51                                           ` Fabrice Popineau
2016-11-30 20:11                                           ` Richard Stallman
2016-11-30 14:48                                         ` Eli Zaretskii
2016-12-09 21:09                                           ` Fabrice Popineau
2016-12-12 17:18                                             ` Phillip Lord
2016-11-11 19:13         ` Jostein Kjønigsen
2016-11-09 17:21   ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2016-11-21 23:35 Fernando Febles Armas
2016-11-22  3:44 ` Eli Zaretskii
2017-01-09  6:33 jsj.register
2017-01-09  7:40 ` Richard Copley
2017-01-10  7:28   ` jsj.register
2017-01-09  7:57 ` Nikolay Kudryavtsev
2017-01-10  7:30   ` jsj.register

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='CAM-tV--vJmuSTEgQY=vnxSqOVy9mr6=UBd=H0VP7gTE8hg5A8Q@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.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 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.