From: Eli Zaretskii <eliz@gnu.org>
To: 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 19:17:39 +0300 [thread overview]
Message-ID: <838ukde4ik.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0jYj1s5Ry+EhcRRD2AK9HqZXCb8UZtoauaqzQWPV=fzXQ@mail.gmail.com>
> Date: Sat, 18 Oct 2014 18:11:53 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 18752@debbugs.gnu.org
>
> > Dani, can you build an optimized version as well next time?
>
> I could, yes. But before, I'd like to understand what are the
> advantages and drawbacks of optimized vs unoptimized builds. Could
> someone explain that to me, or tell me where could I read that
> information?
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.
> Also, what should I do to produce an optimized build? "nt/INSTALL"
> shows an example of how to configure an unoptimized build, but there
> is no example for an optimized one. How about adding that lacking
> example to the file?
If you drop the "CFLAGS=" part, you get an optimized build by
default. The example of that is already in nt/INSTALL, even before
the one that shows how to pass non-default CFLAGS.
next prev parent reply other threads:[~2014-10-18 16:17 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 [this message]
2014-10-18 16:25 ` Dani Moncayo
2014-10-18 17:35 ` Ken Brown
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=838ukde4ik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18752@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--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).