Hacker News new | past | comments | ask | show | jobs | submit login

All of these changes that the author is making are changes that the compiler should be generating.

Unless you work in the embeded systems I don't expect people to have done or needed the % 2048 trick.




The author is writing the compiler (and modifying it to make these changes). What do you mean exactly?


I'm just wowed by this not already being part of V8. What else have they been doing?

I know that V8 has some amazing performance characteristics and if they aren't from doing things that C compilers have been doing for years, then what are these speed boosts coming from?


It might help to read a bit more closely. A lot of the optimisations being discussed were already added years ago; the point is that they are not as useful in real-world usage as they are in benchmarks (or, in fact, disadvantageous).

JIT compiling a highly dynamic language is quite a different task than AOT compiling a statically typed language. Bit-twiddling tricks are unlikely to be the biggest concern. Try starting with the obvious like https://en.wikipedia.org/wiki/Just-in-time_compilation




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: