From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: [SOLVED] (was: very different start up for emacs master compared with 3 month ago)
Date: Tue, 13 Aug 2019 17:29:04 +0300 [thread overview]
Message-ID: <83o90trvf3.fsf@gnu.org> (raw)
In-Reply-To: <87tvale3t6.fsf_-_@mat.ucm.es> (message from Uwe Brauer on Tue, 13 Aug 2019 12:51:33 +0200)
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Tue, 13 Aug 2019 12:51:33 +0200
>
> >> | Version | init file | without init |
> >> |------------------------------------------+-----------+--------------|
> >> | b06917a4912a60402025286d07d4a195749245c4 | 50 sec | 1-2 sec |
> >> | 1d75604eaded6a8482d28d57bc8e6a4d99d5caee | 15 sec | 1-2 sec |
> >>
> >> #+end_src
> >>
> >>
> >> Any idea whats up?
> >>
> >> How can I debug this?
>
> > Bisect your customizations to see which part takes the lion's share of
> > the time, I'd say.
>
> It was my fault. I bisected different commits (using mercurial)
>
> My configuration script was
>
>
> ./configure CFLAGS='-O0 -g3' --enable-checking='yes,glyphs' --enable-check-lisp-object-type --prefix=/opt/emacs27 --with-x-toolkit=athena --with-mailutils
OK, an unoptimized build is expected to be about 2.5 to 3 times slower
than the optimized one.
next prev parent reply other threads:[~2019-08-13 14:29 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 [this message]
2019-08-13 18:46 ` otadmor .
2019-08-13 18:55 ` Eli Zaretskii
2019-08-13 21:10 ` otadmor .
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o90trvf3.fsf@gnu.org \
--to=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 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.