On 7/4/22 09:20, Waldek Hebisch wrote:
If you build sb-fasteval successfully, and it lanuches successfully,
then sb-ext:*evaluator-mode* is already set to :interpret.
'sbcl' behaved differently. Look at message by Jeronimo Pellegrini
from Sun, 7 Jun 2020.
Well, if you are referring to
https://bugs.launchpad.net/sbcl/+bug/1882582
The developer replies that the bug reporter spelled it wrong.
For bytecode compiler, ")time on" reports time that is twice of
the actual time.
We base our time report on Lisp 'get-internal-run-time'.
Could you try adding something like
)lisp (get-internal-run-time)
before and after. And also
)lisp INTERNAL-TIME-UNITS-PER-SECOND
Our time report should be close to difference of values
reported by 'get-internal-run-time' and converted to
normal units based on INTERNAL-TIME-UNITS-PER-SECOND.
For ECL bytecode, I observed that it runs in parallel somehow:
One thread takes 100% CPU and rest threads take a few percent
CPU (total is around 100%), so together it takes 200% CPU.
I wonder if it is the same on your machine.
My ECL version is 21.2.1.
- Qian
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/9268f4d4-e96f-877e-16b2-eee351164467%40gmail.com.
