- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
Sat, 2010-01-23, 22:33
Somehow my latest checkin r20640 has a stability failure on a single
different from correspondant.
...but the commit doesn't touch anything to do with code generation or
the like, so I think it is revealing a pre-existing bug.
We're about to enter interesting times. It's not like we've ever been
swimming in people who understand the backend and optimizer, but now
with iulian focusing on his thesis (which he absolutely should do, don't
get me wrong) we are losing the cleanup hitter at the same time we're
shipping with -optimise turned on by default for the first time ever.
Hard to predict how many more bugs there will be like:
"VerifyError (Register pair contains wrong type) with -optimise compiler option"
I will take up as much slack as I can, but when I already spend all my
time on scala, all I can do is shuffle the time around.