unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, Dani Moncayo <dmoncayo@gmail.com>
Cc: 18752@debbugs.gnu.org, fni-news@pirilampo.org
Subject: bug#18752: 24.3.94; Why is Cygwin Emacs 2x quicker than Windows Emacs?
Date: Sat, 18 Oct 2014 13:35:48 -0400	[thread overview]
Message-ID: <5442A4F4.1000201@cornell.edu> (raw)
In-Reply-To: <838ukde4ik.fsf@gnu.org>

On 10/18/2014 12:17 PM, Eli Zaretskii wrote:
> Unoptimized builds make debugging easier, but are about 2 - 2.5 times
> slower than optimized ones.  For that reason, the usual practice is to
> produce unoptimized builds for snapshots and pretests, but optimized
> ones for official releases.
>
> Latest GCC versions support a -Og optimization switch that gives you
> the best of both worlds.

Do you happen to know how much of a performance difference there typically is 
between -Og and -O2?

Ken





  parent reply	other threads:[~2014-10-18 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 15:04 bug#18752: 24.3.94; Why is Cygwin Emacs 2x quicker than Windows Emacs? Fabrice Niessen
2014-10-17 15:41 ` Eli Zaretskii
     [not found]   ` <86h9z2rb42.fsf-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>
2014-10-17 21:08     ` Fabrice Niessen
2014-10-17 22:12       ` Ken Brown
2014-10-18  5:42       ` Eli Zaretskii
     [not found]       ` <83wq7ydjc7.fsf@gnu.org>
     [not found]         ` <83wq7ydjc7.fsf-mXXj517/zsQ@public.gmane.org>
2014-10-18  6:51           ` Fabrice Niessen
     [not found]         ` <86zjctlvkv.fsf@example.com>
2014-10-18  7:19           ` Eli Zaretskii
2014-10-18 16:11           ` Dani Moncayo
2014-10-18 16:17             ` Eli Zaretskii
2014-10-18 16:25               ` Dani Moncayo
2014-10-18 17:35               ` Ken Brown [this message]
2014-10-18 17:46                 ` Eli Zaretskii
2014-10-18 19:25               ` Stefan Monnier
2014-10-18 19:34                 ` 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=5442A4F4.1000201@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=18752@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=fni-news@pirilampo.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).