From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: npostavs@users.sourceforge.net, jostein@kjonigsen.net,
emacs-devel@gnu.org
Subject: Re: Regarding performance issues with the Emacs 25.1 Windows-build
Date: Mon, 14 Nov 2016 20:12:04 +0200 [thread overview]
Message-ID: <83y40mgccr.fsf@gnu.org> (raw)
In-Reply-To: <87wpg6vw5c.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: emacs-devel@gnu.org, jostein@kjonigsen.net, npostavs@users.sourceforge.net
> Date: Mon, 14 Nov 2016 16:55:27 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It's okay. In general, if you don't strip the binaries, it would be
> > better to also include -g3 in CFLAGS (so that there's debug info
> > there, and reports about crashes can be accompanied by meaningful
> > information), but for a release it is less important than for a
> > pretest, so I see no need for yet another build.
>
> Confused? You mean to have four builds in total?
No, of course not. Just 2: one for x86, the other x86_64.
> Or you want me to configure with:
>
> CFLAGS="-O2 -static -g3"
That's the best if you don't strip the binaries, yes.
Thanks, and sorry for the confusion I caused.
next prev parent reply other threads:[~2016-11-14 18:12 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
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 [this message]
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
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=83y40mgccr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=npostavs@users.sourceforge.net \
--cc=phillip.lord@russet.org.uk \
/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).