[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] gcl safety definition
From: |
Camm Maguire |
Subject: |
[Axiom-developer] gcl safety definition |
Date: |
Fri, 06 Jul 2007 13:03:56 -0400 |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigory ōmae) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI) |
Greetings! 2.7 has a much faster safety mode. I'd like to get some
consensus on how to define it.
Proposal:
safety 1 -- compiled functions and macros check their argument numbers
and types
safety 2 -- inlined function calls in compiled functions and macros
check their argument numbers and types
safety 3 -- all variables and function args of type t, no source inlining, no
branch-elimination, no type propagation. fast-linking is
still permitted.
Separately, which of these should be goverened as well by
compilation-speed and/or speed settings?
Separately, can GCL compilation be considered fast enough if GCL
proper is kept to a small fraction of gcc compilation time?
real time : 71.680 secs
run-gbc time : 15.810 secs
child run time : 48.320 secs
gbc time : 5.640 secs
Take care,
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Axiom-developer] gcl safety definition,
Camm Maguire <=