unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>,
	 emacs-devel@gnu.org
Subject: Re: More build times
Date: Thu, 30 Jun 2022 17:50:47 +0000	[thread overview]
Message-ID: <3b017bf844562da7711b@heytings.org> (raw)
In-Reply-To: <41BC0745-6795-4F6E-8990-CDB29B6A25C7@acm.org>

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]


>> 1362a9fec4 improvement from 130s to 119s (8%) Mattias Engdegård Make 
>> lambda-lifting work again
>
> That just fixed a typo introduced a week or so before, which should 
> cancel it out.
>

Indeed.  The typo in which that typo was introduced was

a350ae058c deterioration from 108s to 129s (19%) Stefan Monnier 
<monnier@iro.umontreal.ca> * lisp/emacs-lisp/cconv.el: Improve line-nb 
info of unused var warnings

And I just checked that fixing that typo in that commit removes the 19% 
slowdown.  This answers one of Lars' questions:

>> a350ae058c deterioration from 108s to 129s (19%) Stefan Monnier 
>> <monnier@iro.umontreal.ca> * lisp/emacs-lisp/cconv.el: Improve line-nb 
>> info of unused var warnings
>
> Hm...  is that something that can be improved (if that code is still 
> there, that is)?
>

  reply	other threads:[~2022-06-30 17:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 12:17 More build times Lars Ingebrigtsen
2022-06-25 13:44 ` Lars Ingebrigtsen
2022-06-25 13:51   ` Tor Kringeland
2022-06-25 14:41     ` Lars Ingebrigtsen
2022-06-25 15:15       ` Andreas Schwab
2022-06-25 14:16   ` Eli Zaretskii
2022-06-25 14:44     ` Lars Ingebrigtsen
2022-06-25 15:16       ` Eli Zaretskii
2022-06-25 15:30         ` Lars Ingebrigtsen
2022-06-29 16:22           ` Gregory Heytings
2022-06-30  8:12             ` Lars Ingebrigtsen
2022-06-30  8:30               ` Gregory Heytings
2022-06-30  8:47                 ` Stephen Berman
2022-06-30  8:49                 ` Lars Ingebrigtsen
2022-06-30  8:42               ` Andreas Schwab
2022-06-30  8:55                 ` Stephen Berman
2022-06-30 16:07               ` Juri Linkov
2022-06-30 16:31                 ` Andreas Schwab
2022-06-30 17:10                   ` Juri Linkov
2022-06-30 13:27             ` Mattias Engdegård
2022-06-30 17:50               ` Gregory Heytings [this message]
2022-06-30 17:53                 ` Gregory Heytings
2022-06-25 14:34   ` Yuri Khan
2022-06-25 14:49     ` Lars Ingebrigtsen
2022-06-26  8:30       ` Stefan Monnier
2022-06-26 15:38         ` Lars Ingebrigtsen

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=3b017bf844562da7711b@heytings.org \
    --to=gregory@heytings.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=mattiase@acm.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).