Killing the Hydra
Apple from the Tree
I try to keep this post short. New update is available:
- MacOSX Darwin PowerPC support is implemented.
- Fixed address distance calculation for the PowerPC native relative branch instructions.
- Refactored the boolean values to use TRUE/FALSE preprocessor defines.
Big thanks goes to Tobias Netzel, who implemented the MacOSX support for the JIT compiling and helped me chasing down one more sneaky bug.
Amiga Workbench Version 1.0 - 2012 concept
How would recreate the "Amiga" "Workbench version 1.0" GUI if you created it today / 2012 ?
Bug! *Splat*
Every developer knows the feeling when finally he/she finds a bug and slaps to the forehead while mumbling: "How on earth was this thing ever been working?..."
Well, it just happened to me, I have fixed a bug that stopped the ROM from booting. It was a rather stupid mistake (as usually); for the details check out the update.
In this other minor update I have fixed one more nuance with the wrong addresses in the dumped PowerPC code log.
The Guru has been taking in riddles again.
Optimize It
I am back from the holidays for sometime now, but I got swamped instantly by the work in my daytime job. I had very little energy on the project in the nights, which was spent on two things: chasing that #@!% bug which is killing me and implementing the data-flow optimization.
JamVM in the making
I have actually received a few donations! I'd like to start by saying thank you, you know who you are!
After a much needed vacation on the French Riviera, I still have a few days off work, and I can put a wee bit more effort into JAmiga/JamVM.
Deluxe Paint
As an Amiga fan, many years ago I used Deluxe paint from Electronic Arts.
Today I still dream that one day, someone, somewhere will create Deluxe Paint for the Amiga.
Looking at JamVM again
In 2009 I had some attempts at JamVM. Now I have actually managed to get JamVM running on AmigaOS 4. You can read more on what was the turning point at amigans.net. So currently I'm going JamVM, all in!
What does this then mean, exactly?
Summertime!
JIT Goes Blue
Byte off more than one can buffer
This is more of a mental note to self. But it gives a small insight to what I'm battling with.
I've just traced in which way VMNetChannel allocates its ByteBuffer (ByteBuffers are used for pretty much anything handling data, not only network stuff, so its a pretty crucial thing to have).
Starting in VMNetChannel, we find a ByteBuffer.allocate(int capacity). It goes something like this:
Back to net stuff
After my latest musings with JNI and JVM interfaces, I am finally back at implementing the network support. I have implemented it pretty like described in previous entry and also made the necessary classpath changes. Furthermore, the classpath implementation, java-net library, now fully depends on the various JVM_-functions exported by the main JAmiga engine, i.e. JVM_Socket, JVM_Bind and so on.