[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Time to merge scratch/correct-warning-pos into master, perhaps?
From: |
Eli Zaretskii |
Subject: |
Re: Time to merge scratch/correct-warning-pos into master, perhaps? |
Date: |
Sun, 23 Jan 2022 07:32:38 +0200 |
> Date: Sat, 22 Jan 2022 20:07:34 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: acm@muc.de, mattiase@acm.org, larsi@gnus.org, monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
>
>
> >>> However the bootstrap is still faster than it was this time last week,
> >>> due to commit 10083e788f7349fa363d100687dc3d94bea88f57 on Thursday.
> >>
> >> That is only true for those who use --with-native-compilation. I
> >> don't.
> >
> > It's supposed to be faster even without native compilation, albeit
> > perhaps not by the same amount.
> >
>
> I don't know, but I just compared 7922131bb2 vs 3b33a14380, and in most
> cases 7922131bb2 is even a bit slower than correct-warning-pos:
>
> make -j1 bootstrap: 654s vs 596s
> make -j4 bootstrap: 256s vs 238s
> make -j8 bootstrap: 201s vs 183s
>
> make -j1 check: 181s vs 162s
> make -j4 check: 45s vs 40s
> make -j8 check: 26s vs 23s
Is that an optimized or an unoptimized build of Emacs?
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, (continued)
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/24
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/24
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/24
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/24
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/25
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/25
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Eli Zaretskii, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?,
Eli Zaretskii <=
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Gregory Heytings, 2022/01/23
Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Stefan Monnier, 2022/01/15
Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Brahimi Saifullah, 2022/01/15
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/16
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Brahimi Saifullah, 2022/01/16
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Brahimi Saifullah, 2022/01/22
- Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Alan Mackenzie, 2022/01/23
Re: Time to merge scratch/correct-warning-pos into master, perhaps?, Andrea Corallo, 2022/01/17