On 10/15/23 23:19, Waldek Hebisch wrote:
Well, I noticed the issue tooking at build time, but this is really general problem: - sbcl compiler is slow (takes a lot of time to generate code) - default sbcl interpreter is slow too Most things that we pass to sbcl eval is trivial, so slow interpreter is still significantly faster than compilation+compiled runtime.
I would argue that compiling such trivial things passed to eval is fast enough that is undetectable by human. SBCL is designed to compile everything (including in REPL) by default.
Note that if you put your loop in a function, it will be compiled and run at compiled speed. I feel that such loops on command line are rare enough that our current setting is better than sbcl default.
Running loops in interpreter is a common use pattern, and running loops with millions of items (and filter them) is not uncommon. - Qian
Concerning build time: using interpreted eval gave us significant speedup, but not using eval is faster, so a lot of evals in compiler are removed (replaced by different code). But for handling code generated by FriCAS interpreter use of eval is currently unavoidable...
-- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to fricas-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/a46ec522-e423-41c2-812a-54b17d069cb1%40gmail.com.
