unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Arthur Miller <arthur.miller@live.com>,
	Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Compilation speed
Date: Tue, 11 Aug 2020 19:11:55 -0700	[thread overview]
Message-ID: <cf822f70-68ff-a8f4-9b65-04b5ad277f53@cs.ucla.edu> (raw)
In-Reply-To: <VI1PR06MB4526936479704BAFA9A35D6796440@VI1PR06MB4526.eurprd06.prod.outlook.com>

On 8/10/20 7:33 AM, Arthur Miller wrote:

> Since Emacs requires C99 compiler (as I understand) couldn't configure
> script just check for avialability of C99 standard, OS and compiler and
> assume the headers, flags and certain functions are avialable?

Unfortunately not. Lots of implementations conform mostly to C99 but have some 
exceptions. So we can't have a single C99 test; we need individual tests to 
cover the exceptions.

That's not to say we couldn't prune 'configure'; we could. It has several tests 
that are no longer relevant on today's porting targets. The problem is finding 
the developer time to prune them. There's a lot of good stuff there mixed in 
with the cruft.

> if there is for example not strnlen
> function avialable, would it be copied/added to system to by autotools

Generally speaking the autotools don't mess with your dev-chain installation, 
for understandable reasons.

> Couldn't autotools devs, make those tests run in their
> own shell as asynchronous processes, write output to a file and then
> make a finall pass over all outputs and then decide to bail out/continue
> or take an action.

Yes, but this would require quite a rewrite, as existing scripts typically don't 
say which tests depend on which other tests' results. I'm not saying it couldn't 
be done, only that it wouldn't be that easy.



  reply	other threads:[~2020-08-12  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 15:20 Compilation speed Lars Ingebrigtsen
2020-08-06 19:07 ` Paul Eggert
2020-08-19  9:25   ` Mario Lang
2020-08-19  9:43     ` tomas
2020-08-19 12:37       ` Ergus
2020-08-06 22:14 ` Stefan Monnier
2020-08-07  6:55   ` Lars Ingebrigtsen
2020-08-07 16:26   ` Andrea Corallo via Emacs development discussions.
2020-08-10 14:33 ` Arthur Miller
2020-08-12  2:11   ` Paul Eggert [this message]
2020-08-12 12:53     ` Arthur Miller
2020-08-12 16:08       ` Stefan Monnier
2020-08-12 16:59       ` Paul Eggert

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=cf822f70-68ff-a8f4-9b65-04b5ad277f53@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).