>>> "EB" == Eric Blake <[EMAIL PROTECTED]> writes:
>> The non-use of frozen files is probably just the result of laziness: >> it's too hard to set up and use. If we had autom4te instead of m4 >> directly, we would probably use frozen files. I have no idea what >> the speed-up would be though. > Here's some quick profiling numbers, executed on cygwin, using > autoconf.git's current m4sugar with branch-1.6 of m4, and picking the best > time from several runs each: > $ time m4 /dev/null # Do nothing, for reference > real 0m0.062s > user 0m0.030s > $ time m4 -I lib m4sugar/m4sugar.m4 /dev/null # Load m4sugar from scratch > real 0m0.140s > user 0m0.093s > $ m4 -F f.m4f -I lib m4sugar/m4sugar.m4 # Freeze... > $ time m4 -R f.m4f /dev/null # then load m4sugar from frozen > real 0m0.063s > user 0m0.030s But I guess that in the case of Bison, most of the cost is really in the "runtime" part, not the "load it all" part. Yet it would be interesting to make a try. I'll see if I can try that.
