New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "The Road to the JIT" #2
Conversation
allowed customers to compile their time-critical modules to native code | ||
and all other modules to threaded BEAM code. The threaded BEAM in | ||
itself was faster than JAM code. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be interesting if you can write something about why threaded BEAM was faster than JAM (if there is some important difference).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that is outside the scope of this blog post. If there is interest, I could write a separate blog post later.
used). At one of our meetings between the HiPE team and the OTP | ||
team, I remember [Richard Carlsson][richcarl] pointing out to me that it would | ||
be nice for [Wings3D][wings3d] to have floating point literals. The | ||
OTP team implemented literal pools in OTP R12. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not clear to me if floating point literals have any connection to literal pools.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Floating point constants are stored in the literal pool.
No description provided.