From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: CHECK_STRUCTS/dmpstruct.h mechanism is broken. Date: Mon, 15 Apr 2019 11:31:25 +0000 Message-ID: <20190415113125.GA6213@ACM> References: <9809d5ce-c1c4-48e9-6dac-489431b34067@cs.ucla.edu> <671ba8dd-894b-5698-d162-8901b1098b9a@cs.ucla.edu> <83k1g04al8.fsf@gnu.org> <93b861b3-41d2-e590-d4b8-46a4bb64bfe8@cs.ucla.edu> <8736mmxr2e.fsf@Rainer.invalid> <87h8b1yrsi.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="63702"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.10.1 (2018-07-13) Cc: Achim Gratz , emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 15 13:31:54 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hFzq6-000GR4-Ag for ged-emacs-devel@m.gmane.org; Mon, 15 Apr 2019 13:31:54 +0200 Original-Received: from localhost ([127.0.0.1]:48570 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hFzq5-0005a6-7l for ged-emacs-devel@m.gmane.org; Mon, 15 Apr 2019 07:31:53 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49631) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hFzpw-0005YC-3Z for emacs-devel@gnu.org; Mon, 15 Apr 2019 07:31:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hFzpp-0000wi-Cx for emacs-devel@gnu.org; Mon, 15 Apr 2019 07:31:39 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:27041 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1hFzpk-0000sH-87 for emacs-devel@gnu.org; Mon, 15 Apr 2019 07:31:35 -0400 Original-Received: (qmail 62923 invoked by uid 3782); 15 Apr 2019 11:31:27 -0000 Original-Received: from acm.muc.de (p4FE15DF8.dip0.t-ipconnect.de [79.225.93.248]) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 15 Apr 2019 13:31:25 +0200 Original-Received: (qmail 6217 invoked by uid 1000); 15 Apr 2019 11:31:25 -0000 Content-Disposition: inline In-Reply-To: X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 193.149.48.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:235477 Archived-At: Hello, Paul. On Sun, Apr 14, 2019 at 16:29:50 -0700, Paul Eggert wrote: [ .... ] > Parallelizing Autoconf is a much bigger project than transitioning GNU > Emacs away from Autoconf, and nobody has seriously proposed attempting > it. Any reason why not? Is there anything particular about Autoconf that makes it difficult to parallelise, or is it just a case of nobody stepping up to do the work? Given how prevalent Autoconf is, and the fact that processors with several cores have been the normal thing for so long, and that these are being superseded by processors with many cores, surely making configure run its things in parallel would be a very productive use of time and effort. -- Alan Mackenzie (Nuremberg, Germany).