From: "otadmor ." <otadmor@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: [SOLVED] (was: very different start up for emacs master compared with 3 month ago)
Date: Wed, 14 Aug 2019 00:10:50 +0300 [thread overview]
Message-ID: <CAJd1wGK9rHQKaVcXLVBQ=cpNpbS5_nwhdVu3MwF-Hmb2qGwnbw@mail.gmail.com> (raw)
In-Reply-To: <83blwssxn0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Are there any known issues with Ofast?
On Tue, Aug 13, 2019, 21:56 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: "otadmor ." <otadmor@gmail.com>
> > Date: Tue, 13 Aug 2019 21:46:48 +0300
> > Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
> >
> > When compiling emacs for daily use is it better to compile with -O? Or
> without -O at all?
> > Which optimization level is suggested?
>
> Using -O0 produces a binary that's slower, but if it crashes or you
> need to debug it, the information you can report is more full and
> reliable. Letting the build use the default optimization produces a
> faster program, but it's harder to debug.
>
> What to do is up to you. I debug the development version of Emacs
> quite a lot, so I always build the development snapshots with -O0.
>
[-- Attachment #2: Type: text/html, Size: 1361 bytes --]
next prev parent reply other threads:[~2019-08-13 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 15:47 very different start up for emacs master compared with 3 month ago Uwe Brauer
2019-08-09 16:05 ` Eli Zaretskii
2019-08-13 10:51 ` [SOLVED] (was: very different start up for emacs master compared with 3 month ago) Uwe Brauer
2019-08-13 14:29 ` Eli Zaretskii
2019-08-13 18:46 ` otadmor .
2019-08-13 18:55 ` Eli Zaretskii
2019-08-13 21:10 ` otadmor . [this message]
2019-08-14 2:36 ` Eli Zaretskii
2019-08-14 5:19 ` otadmor .
2019-08-14 14:24 ` 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='CAJd1wGK9rHQKaVcXLVBQ=cpNpbS5_nwhdVu3MwF-Hmb2qGwnbw@mail.gmail.com' \
--to=otadmor@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).