From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Sean Sieger <sean.sieger@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Failed to compile from last bzr repo
Date: Tue, 5 Apr 2011 00:00:02 +0200 [thread overview]
Message-ID: <BANLkTim3Qkyu4N70-HUUhwTc7SU1c0rRXg@mail.gmail.com> (raw)
In-Reply-To: <jwvpqp1zo0q.fsf-monnier+emacs@gnu.org>
On Mon, Apr 4, 2011 at 23:51, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> On one of my setups it takes about 4mins (8 dual core AMD chips help),
Now I'm envy.
> takes just a tiny bit loner (especially with -O0 and all assertions
> enabled).
Because of it being slower during all the .el compilations, you mean?
I regularly build both -O2 --enable-checking and -O0 --enable-checking
and I haven't seen much difference, but now I'm curious.
Juanma
next prev parent reply other threads:[~2011-04-04 22:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 9:46 Failed to compile from last bzr repo Bastien
2011-04-04 11:53 ` Eli Zaretskii
2011-04-04 12:22 ` Deniz Dogan
2011-04-04 12:38 ` Sean Sieger
2011-04-04 17:37 ` Eli Zaretskii
2011-04-04 21:19 ` Juanma Barranquero
2011-04-04 21:51 ` Stefan Monnier
2011-04-04 22:00 ` Juanma Barranquero [this message]
2011-04-05 13:14 ` Stefan Monnier
2011-04-05 15:39 ` Sean Sieger
2011-04-05 16:36 ` Juanma Barranquero
2011-04-05 16:52 ` Eli Zaretskii
2011-04-05 22:45 ` Juanma Barranquero
2011-04-06 3:01 ` Eli Zaretskii
2011-04-06 3:22 ` Juanma Barranquero
2011-04-06 12:57 ` Andy Moreton
2011-04-06 13:32 ` Eli Zaretskii
2011-04-06 14:18 ` Juanma Barranquero
2011-04-06 15:47 ` Eli Zaretskii
2011-04-06 16:08 ` Eli Zaretskii
2011-04-06 16:18 ` Juanma Barranquero
2011-04-05 15:41 ` Sean Sieger
2011-04-05 20:57 ` Stefan Monnier
2011-04-05 0:13 ` Sean Sieger
2011-04-05 2:59 ` Eli Zaretskii
2011-04-04 16:39 ` Stefan Monnier
2011-04-04 17:35 ` Eli Zaretskii
2011-04-04 16:26 ` Bastien
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=BANLkTim3Qkyu4N70-HUUhwTc7SU1c0rRXg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sean.sieger@gmail.com \
/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.