GNU bug report logs -
#80065
[PATCH 1/1] Have default 'compile-command' run make in parallel
Previous Next
To reply to this bug, email your comments to 80065 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#80065; Package
emacs.
(Tue, 23 Dec 2025 18:26:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Philip Kaludercic <philipk <at> posteo.net>:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org.
(Tue, 23 Dec 2025 18:26:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I have been using this in my personal configuration for a few years now,
and I think it might be nice to consider this upstream as well. To my
knowledge, all real-world "make" implementations support the "-j" flag.
[0001-Have-default-'compile-command'-run-make-in-paralle.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#80065; Package
emacs.
(Tue, 23 Dec 2025 18:35:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 80065 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
To be nice to unsuspecting users, this might default to (/ (num-processors)
2) or -2. I have 16 cores and limit to 10 or 12 usually.
On Tue, Dec 23, 2025 at 1:26 PM Philip Kaludercic <philipk <at> posteo.net>
wrote:
>
> I have been using this in my personal configuration for a few years now,
> and I think it might be nice to consider this upstream as well. To my
> knowledge, all real-world "make" implementations support the "-j" flag.
>
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#80065; Package
emacs.
(Tue, 23 Dec 2025 19:01:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 80065 <at> debbugs.gnu.org (full text, mbox):
Stéphane Marks <shipmints <at> gmail.com> writes:
> To be nice to unsuspecting users, this might default to (/ (num-processors)
> 2) or -2. I have 16 cores and limit to 10 or 12 usually.
Right, I would suggest something like (ceiling (num-processors) 2) to
avoid edge-cases on single-core and dual-core systems:
(ceiling 1 2) ;=> 1 (#o1, #x1, ?\C-a)
(ceiling 2 2) ;=> 1 (#o1, #x1, ?\C-a)
(ceiling 3 2) ;=> 2 (#o2, #x2, ?\C-b)
(ceiling 4 2) ;=> 2 (#o2, #x2, ?\C-b)
...
> On Tue, Dec 23, 2025 at 1:26 PM Philip Kaludercic <philipk <at> posteo.net>
> wrote:
>
>>
>> I have been using this in my personal configuration for a few years now,
>> and I think it might be nice to consider this upstream as well. To my
>> knowledge, all real-world "make" implementations support the "-j" flag.
>>
>>
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#80065; Package
emacs.
(Tue, 23 Dec 2025 19:14:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 80065 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Tue, Dec 23, 2025 at 2:00 PM Philip Kaludercic <philipk <at> posteo.net>
wrote:
> Stéphane Marks <shipmints <at> gmail.com> writes:
>
> > To be nice to unsuspecting users, this might default to (/
> (num-processors)
> > 2) or -2. I have 16 cores and limit to 10 or 12 usually.
>
> Right, I would suggest something like (ceiling (num-processors) 2) to
> avoid edge-cases on single-core and dual-core systems:
>
> (ceiling 1 2) ;=> 1 (#o1, #x1, ?\C-a)
> (ceiling 2 2) ;=> 1 (#o1, #x1, ?\C-a)
> (ceiling 3 2) ;=> 2 (#o2, #x2, ?\C-b)
> (ceiling 4 2) ;=> 2 (#o2, #x2, ?\C-b)
> ...
>
> > On Tue, Dec 23, 2025 at 1:26 PM Philip Kaludercic <philipk <at> posteo.net>
> > wrote:
> >
> >>
> >> I have been using this in my personal configuration for a few years now,
> >> and I think it might be nice to consider this upstream as well. To my
> >> knowledge, all real-world "make" implementations support the "-j" flag.
>
Might want to make compile-num-processors a defcustom or defvar so one can
override in their .dir-locals.el for a project or specific directory? That
could be an integer or a function, I guess.
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org:
bug#80065; Package
emacs.
(Tue, 23 Dec 2025 20:26:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 80065 <at> debbugs.gnu.org (full text, mbox):
Stéphane Marks <shipmints <at> gmail.com> writes:
> On Tue, Dec 23, 2025 at 2:00 PM Philip Kaludercic <philipk <at> posteo.net>
> wrote:
>
>> Stéphane Marks <shipmints <at> gmail.com> writes:
>>
>> > To be nice to unsuspecting users, this might default to (/
>> (num-processors)
>> > 2) or -2. I have 16 cores and limit to 10 or 12 usually.
>>
>> Right, I would suggest something like (ceiling (num-processors) 2) to
>> avoid edge-cases on single-core and dual-core systems:
>>
>> (ceiling 1 2) ;=> 1 (#o1, #x1, ?\C-a)
>> (ceiling 2 2) ;=> 1 (#o1, #x1, ?\C-a)
>> (ceiling 3 2) ;=> 2 (#o2, #x2, ?\C-b)
>> (ceiling 4 2) ;=> 2 (#o2, #x2, ?\C-b)
>> ...
>>
>> > On Tue, Dec 23, 2025 at 1:26 PM Philip Kaludercic <philipk <at> posteo.net>
>> > wrote:
>> >
>> >>
>> >> I have been using this in my personal configuration for a few years now,
>> >> and I think it might be nice to consider this upstream as well. To my
>> >> knowledge, all real-world "make" implementations support the "-j" flag.
>>
>
> Might want to make compile-num-processors a defcustom or defvar so one can
> override in their .dir-locals.el for a project or specific directory? That
> could be an integer or a function, I guess.
I figure that the complications of having the default value of one user
option depend on that of another is not worth the fuss, especially when
we consider that `compile-command' is already local safe.
This bug report was last modified 1 day ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.