To sum up what you will get with the new beta: mainly bugfixes. All the features are locked down for the release, the ticket list for release 1.0 is practically empty. I am waiting for any bugs you find before the release. So, please do report bugs you find. But again: it is very important to try to verify the issue before you decide about reporting it. Please follow the steps which are documented in the README file.
Your efforts are greatly appreciated.
JIT compatibility diagnostics
I have rejected a few bugs due to the fact that these programs are not compatible with the current JIT compiling implementation. The reason is very simple: if the program is trying to modify itself without flushing the instruction cache properly then the modified code won't be recompiled and the program will misbehave. Like this program: Where Time Stood Still.
These programs might work on a real processor and still fail with the JIT compiling because the cache handling is not emulated exactly the same how it would behave on a real processor. (Namely: the number of cache lines are much larger than on a real processor, so more code is "cached".)
Although this is not ideal, but for now only a handful of programs are depending on the cache size, so it won't cause too much trouble.
How could you tell that the program is compatible with the JIT compiler?
That is a very valid question. And here is the answer: there is a option for that! (At least there is now.)
I have wasted so much time on chasing errors coming from this issue that finally I have decided I implement a diagnostic configuration option for it. It is called: comp_test_consistency
Usual disclaimer: read the documentation and if you didn't understand what does it do then don't turn it on.
Actually, it is pretty simple: in addition to every compiled block of instructions the compiler also compiles a check which compares the original content of the memory which was used for the compiling to the current content. If it doesn't match then the emulation stops.
Basically, it can be used for verifying if the program misbehaves because it does not flush the instruction cache properly, or there is some other reason.
It is safe to keep it turned on, but it slows down the emulation (sometimes considerably), so use it only when it is needed.
As I already announced in the previous post (couple months ago): the Amiga X1000 optimized version is available in the package. Please use only that version on Amiga X1000, the generic build won't work properly.
Due to the "popular demand" (more than one request ;) I have fixed the cache handling of the emulated 68060 processor type. Please note: it is stated in the documentation from the original E-UAE that the 060 support is not implemented and all I had done was: fixed the cache bits to let the emulator turn on the caches, so the JIT can be activated. However, it is highly likely that there will be problems with some programs running on 060, since other important aspects of the 060 is not implemented (like proper stackframe). So, watch your steps while using it. (And please don't report bugs for it. kthxbai)
ChrisH kindly implemented the support for the betas in RuninUAE. You can turn on the JIT emulation from the menu now. (You guys are too spoiled!) Thanks Chris!
In case you haven't heard: WinUAE is capable of emulating PowerPC hardware through QEmu on intel compatible processors and run PPC apps and even AmigaOS4.
The obvious question: how much better would it be running PowerPC programs on actual PowerPC processor under hardware emulation? :) Probably it would be possible to make use of the native PowerPC processor and it would be fast. Very fast. Not to mention it would open the door for AmigaOS4 running on Macintosh iBooks for example. Do I have plans implementing it? No, sorry. Thanks for asking.
Finally, some thank-you's to the lovely people who helped me in this beta.
Big thanks goes to: MickJT, Mike Blackburn,Chris Handley, Luigi Burdo, Samir Hawamdeh, Raziel and Cass.
Some guys just can't stay away as it seems. :) See you soon.
After I had done some investigation, it turned out that MickJT was right for a long time. We don't need unique changes for Amiga X1000 (for the P.A. Semi PA6T processor), because it is similar to the already supported G5 (PowerPC 970) processor.
So, I have decided that we must not delay the beta for Amiga X1000 any longer. This new build is exactly the same Beta #4 release feature-wise; which was done for the other platforms already. Except that it is compiled for AmigaOS4 with the same minor changes which increase the performance on G5 significantly.
Since the code base is the same I kept the same beta version tag with a postfix. For the first and the last time... Úttörő becsület szavamra! :)
This build is not fully optimized for PA6T processor, since there is no support for that processor target in the AmigaOS4 SDK yet. It is still running much better than the previous generic builds.
Hopefully the PA6T support will be resolved sooner or later in the SDK and then I will add any necessary changes to the E-UAE build too.
In the meanwhile the binary for this build target will be added to the upcoming releases.
Actually, the credit goes to the following good people:
Tobias Netzel - who implemented the G5 support and helped MickJT with advices;
MickJT - who was experimenting with the build for a long time already and pushed me to do this release;
Sven Ottemann & Sebastian Bauer - who helped me with the documentation for PA6T;
Tommysammy - who was kindly doing the testing.
This was a blindfolded build again: I have no access to an Amiga X1000, so I couldn't test the build by myself.
I would like to invite all Amiga X1000 owner to give me some feedback regarding the performance or any issues what turns up with this special build.
You can find my email address at the end of the README file.
Four is a nice, round number. Power of 2, not too many, not too less. You know, four is referring to many good things, like: the Fantastic Four, 4th of July, AmigaOS4, The Magnificent Four... Err.. Maybe not that, scratch that last one.
I had an irresistible urge to RickRoll you guys with the link, but that video has been blocked recently on YouTube in many countries, so maybe next time.
I had my sweet time with a very weird bug related to Quake, which is not resolved yet and probably related to the failure to implement the soft cache flushing. These two tickets are pushed back to Beta #5 for now. Previously I had no intention to do one more beta release before the first Release Candidate, but as it seems I need one more round of testing period.
I had to shuffle around some tickets while I was rethinking the upcoming Release Candidate. You know, changing priorities, agile development, whatnot. What is listed in the milestones now is the plan, although it is not set in (mile)stone... Heheh... (Huh, that was a really lame pun. You should do better than that!)
The idea is: I am going to fix every issue which is known and give you guys some time to test before the final release (candidate).
After a few rounds of pushing and pulling some SAM440/Flex related codes hopefully we have sorted out all the various problems related to those machines. If you were still experiencing issues then please let me know.
Thanks to Tobias Netzel, the flag extraction on G5 is fixed, this will resolve a number of problems with various programs.
The compiling for G5 is still not resolved for MorphOS,
no G5-optimized binary again, sorry guys. If you could tell me how can I
(easily) compile the files for G5 on my iBook then I give it a go, I promise.
As you can see: Beta #5 is coming, there are already a handful things lined up for it.
Please do test Beta #4 and please do report bugs you have found. It is important to sort out as many problems as I could. It is equally important to help me reproducing the bug. So, please read the instructions. Thanks a bunch!
I would like to give a big thanks to Luigi Burdo.
He helped me with a great deal of things, reported lots of bugs and he
is so enthusiastic that he inspired me to keep walking on the road. Thanks a lot, Luigi! Keep up the good spirit!
And, of course, my dearest sidekicks, who just couldn't stay away from the project: MickJT and Tobias Netzel. Cheers!
Also would like to thank the helps, bug reports and overall support to: Samir Hawamdeh, Kicko, Chris Handley, Allan Ullmann.
Ladies and Gentlemen, I would like to have a word with you about bug reporting...
Please do not report E-UAE JIT compiling related bugs to:
a forum at your favorite portal(because they are going to give you advices, unless it is a cooking portal, but they won't fix it anyway);
your "friends" on Facebook as a status post(because your hot ex-classmate doesn't care, not to mention that she put you to the acquaintances list for a long time and I am prettty sure she won't fix it anyway);
Runinuae author(because although Chris is a good guy, almost certainly he won't fix it anyway - hey Chris!);
your fellow Amiga-enthusiasts at the Club(because they might listen to your theory on what is the root cause of the bug, but they won't fix it anyway);
your neighbor's cat(because the poor thing doesn't want to hear anything about "fixing", I guarantee).
Why? Quite simple: if you try to report bugs anywhere else than my mailbox there is zero guarantee that your bug report ever lands on my computer.
You know, there is some chance that I wake up one day and realize:
Ah, some Amiga-fan while playing Superfrog on level 6 encountered a graphical glitch which is caused by a mis-used flag dependency in the JIT compiler optimization, so I must fix it. I need coffee!
Yes, there is some chance, very-very-very low chance. (As opposed to there is high chance that I wake up one day and realize: Hrrgrhh... I need coffee!)
If you want to get the bug fixed then report it to me, preferably by e-mail.
I held this release back for a while just to fix the emulated cache checksum feature, but I have been chasing a bug for two weeks without any success. So, that fix is postponed to the next beta, in the meanwhile you can enjoy some significant speed enhancement and increased stability.
Without going into the details regarding the changes (see the included README for all changes) I would like to mention the most important change:
The major feature of this beta release is the register and flag optimization fix. You can turn it on in the configuration, just set comp_optimize to true.
If you are interested in the details I explained it already how the optimization works in an earlier post, but in case you are too lazy to read through that post: here is my old diagram (just because it is beautiful, you know):
Code translation flow diagram
Let me summarize it for you: the JIT compiler is collecting information about data-flow dependencies between the various macroblocks and tries to remove the ones which won't have any effect on the outcome of a certain block of macroblocks.
This is not a new feature in the JIT implementation, but previously a few (tons of) bugs prevented it from working on more complex codes than my Mandelbrot test.
In this release I have fixed every issue I have found so far with the optimization and it seems working quite nicely. You can boot the AmigaOS and it runs just fine, also games and demos will benefit from this feature too.
I was planing to do a comparison video where the speedup is clearly shown, but I haven't had too much time yet, so this is your job now, dear EUAEPPCJIT fans! Just post the links to the videos into the comments here. :)
PPC970 aka G5
Not everything is sunshine and happiness, though. Supporting G5 processor architecture target turned to be much more complicated than I thought, especially because I don't have any hardware to test on.
In the previous release the MacOSX G5 binary was not working properly on G5 (neither on any other PowerPC as matter of fact). Thanks to Luigi Burdo for the report and Tobias Netzel (again) for the help with the compiler. This is fixed in this release, hopefully. (Fingers crossed, I still don't have hardware to test on.)
While the situation with the MorphOS G5 version is not that hunky-dory: as it seems there is no official compiler with G5 support yet in the MorphOS SDK and it is rather complicated and unreliable to compile any source for that processor. Until this situation is improved the G5 version for MorphOS won't be available from the beta binaries.
However, nothing stop you from compiling your own version from the sources, as these are always available at SourceForge.
As I mentioned: I postponed the fix for the block checksum to the next release and also picked up some things to do. You can find the planned list here:
We have just arrived to another exciting milestone on the long road: all the important instructions for the initial release are implemented under the JIT compiling.*
Lots of bugs were fixed, the emulator is much more stable now than the initial beta release.
Some new features are added too: I have merged the SAM440EP/Flex support (thanks to Soft3) and the CGX overlay for MorphOS (thanks to Thunder and Fab). See configuration documentation regarding how to set the overlay up.
As I already mentioned in the previous post: this beta release was delayed for a couple weeks due to a bug that slipped into the code base long time ago. It was discovered on Mac first, but I was able to reproduce it on MorphOS too. Took me a while to figure out what was going on, but it is fixed now.
This was a very tricky bug, it could be blamed for random crashes and endless loops also, not only on Mac, but on all supported platforms. It was triggered randomly based on the distance between the main application code and the code buffer in memory. (Thanks to Mike for discovering this right before I released the beta.)
I have spent a significant amount of time on figuring out how can I do the build for all supported platforms (AmigaOS4, MorphOS and MacOSX-PPC) using my environments. It wasn't easy, but finally I managed to do most of the release on my own.
As it seems MorphOS SDK does not support G5 yet, so I was not able to do the compiling by myself, but thanks to Fab the G5 executable is also available in the release package.
So, as of now users on all major supported platforms can grab the package and start using the right version.
(Sorry, Linux and BSD folks, you are still on your own.)
And the World trembled...
...or at least that tiny part which I am involved in when I am wearing my crazy latex suitwith a huge letter "A" on my chest for my secret identity: the Amiga Software Developer.
After the first beta release forum posts, emails, news sites, blogs had risen in an enormous unmanageable thunderstorm, struck on me with insane amount of communication. (While the rest of the World barely noticed what have just happened.)
Finally I crawled through messages from every possible (and impossible) source and answered the questions to my best knowledge, accepted the good advices, kindly rejected some nonsense.
Since I received tons of feedback (good and bad), I inclined to draw some conclusions from the reaction to the very first beta release. Here is the summary for your benefit:
Some people don't understand how the JIT works and what is the exact purpose of it. All I can say is: please read the documentation... Some other (knowledgeable) folks stood up on the forums and educated the others, well done! I hope this helps, because I really don't have time to deal with it.
Many of the users have irrational expectations for how much the JIT compiling will speed up the emulator. (According to somebody: it supposed to be "ten times faster than the interpretive"... Err... Not likely. How did they come up with any number anyway?)
Well, the implementation is not finished yet, some of you guys don't really understand the concept of "beta release". Okay, I admit I was cheating a bit: technically the JIT compiler wasn't feature-complete when the first beta was done. Yet the remaining pieces were related to not too often used instructions anyway.
For the second beta the instructions are done*, yet there is clearly room for improvement regarding some bugs. Probably as soon as I will be able to fix up the optimization of the register- and flag-flow there will be a significant bump for the speed. (No, not "ten times" fold.)
It is hard to measure how much faster the programs are running and some lovely people baffled on this too. Since there is usually no obvious visual clue for the speedup and a 30%-50% increase in the processor speed is probably hard to notice while your favorite jump-and-run game is jumping and running.
Yet, you can feel that the whole emulation is more snappy than before probably even when you simply run Workbench. Except when it crashes. But even then: it crashes 30%-50% faster! :)
Too bad that some good souls are obsessed with their favourite game/program and keep saying that the JIT is worthless because it doesn't make any difference for that particular piece of software. As it seems this JIT compiling is not for you then.
There was one more interesting thing what I have noticed too late unfortunately: G5 support for MorphOS. Since I don't have a G5 machine I never considered that there is a need for that. But there were some murmur about the speed of the MorphOS version on G5 on some forums. No wonder: it needs a special version, which can be compiled from the sources for some time now. (Thanks to Tobias Netzel and to Fab for the special build.)
Probably the same applies to the PA Semi processor and the Amiga X1000, but I don't have that one either. (Donations? :)
Also the mysterious support for SAM440EP/Flex, what I have never heard of before. No wonder it was missed.
Fun fact from the Outer World: I tried to explain to my colleagues how I spent my Summer vacation. However, I am significantly older than almost any of them, so they were looking at me with confusion in their eyes mixed with a little pity. "Yea, my father loves fooling around with those old machines too!" - was one of the comments. Well put, Sir, well put.
To make you (some other geeks around the World) happy: here is the new beta...
In case you stop reading here (or you already skipped the first cheesy part):
as always, please read the README for your comfort and safety. Thanks.
Since I bought an iBook for 50 NZD, now I can produce the MorphOS and the MacOSX versions too which were also included in this release together with the AmigaOS4 version. (And by buying a Mac I broke one of my principles: no Apple product crosses the door of my house. I hope you guys are content what you were doing...)
I must admit I have learned a lot in the past month about the sorry state of the E-UAE project. I didn't know what is the current situation of the various binary releases until I received some references to modified AmigaOS4 and MorphOS binary versions.
I guess this is the destiny of any abandoned open source project: lots of good people is trying to improve it, but nobody is standing up and takes over the maintenance of the project.
Well, I am of the same kind, as it seems. It was never my goal to take the ownership of the E-UAE project or fork it into a new iteration.
However, as soon as I released the first beta of the JIT compiled version the watching eye of the public turned to my little scared pet project and I received lot of questions about whether this-or-that particular fix from various developers were included or not. (Mostly not.)
To satisfy at least some part of the user base I tried to gather the various fixes from every corner of the Internet and applied them on the source code. This means no way new base source repository for the E-UAE project, but at least it will help whoever wants to grab the torch and probably it will be useful for you, dear user in the meanwhile in the form of the beta releases.
As of now I switch from batch release strategy to immediate update. This means: I will commit each change one by one to the SourceForge repository as soon as the change is ready instead of buffering up lots of changes locally and commit them in a big changeset.
So, if you look for the repository changesets and the tickets then you can watch the progress of the project closely.
I also make use of the tickets in the completion of the various fixes and tasks:
I added milestones to the tickets, so you can get a feeling of the upcoming beta and the included changes, fixes. Open tickets are defining the majority of the outstanding work. I am currently working on the accepted ticket, while pending tickets are already committed to the repository, but not released in binary form yet. Released tickets are the closed ones.
For PPCJITBET03 you can find the planned changes here:
There is also a milestone named "PARKED" which is a holding box for the various bugs and problems that are not considered for this project (yet).
Finally, big thanks goes to: Thunder, kas1e, MickJT, Fab, Tobias Netzel and Mike Blackburn for helping me with lots of things regarding bug finding, fixing, platform support and constantly watching out for the updates on the repository.
I am still waiting for any (detailed) bug reports, just have a good read of the README file before you jump to your email client.
Footnote *There is a fine print here: I was
struggling with CMP2 instruction and finally I gave up after a couple
days. The binary code for the instruction is bundled with CHK2 and I
couldn't figure out how solve the exception handling for that. So, this
instruction remains unimplemented for now, not a big deal luckily.
But what a year! Yes, finally we are getting very close to the Real Thing(tm). Even a beta version is available from the project, although probably it is not particularly useful to anybody who is not the adventurous type. There are many bugs to chase and also there is room to improve.
I know everybody is eagerly waiting for the second beta. It was prepared more than two weeks ago, the sources are released to SourceForge, the post is ready to launch...
But then suddenly Mike Blackburn came back to me (big thanks for that) and mentioned a show-stopper bug on Mac. In the meanwhile I confirmed that the same bug does exist on MorphOS too, so probably it is just a coincidence that the emulation works on AmigaOS4.
Right now I am trying to figure out what is going on, but for that I needed access to a Mac. So, it took me a while to set up everything and getting ready to debug this. After spending a couple days on chasing my own tail already I am no closer to the solution yet, but I promise I put all my free time into this.
Please relax and enjoy the beautiful Summer at the Southern Hemisphere and try not to freeze to death in the Winter at the North.
I wish all of you guys an awesome happy new year for 2014!
We made it this far, there was no nuclear holocaust yet, which is an amazing achievement for the human race considering our lovely nature. Well done. And now something completely different, but almost equally exciting (probably for much less human beings, can't speak for aliens)... I woke up in the morning and had a look at the clock and it showed me:
Yes, it is unbelievable, I know. After this long-long waiting finally here it comes. And it even comes with bugs! Lots of it!
Now seriously, if you are interested in testing the PowerPC JIT then go and get your binary release from the SourceForge page:
Tiny catch: at the moment only the AmigaOS4 version is available. See below.
You might also need a previous distribution which includes all the tools, like transrom, mousehack, make-hdf, etc. I tried to compile these, but somehow the cross-compiling failed and I ran out of patience.
What is included in beta01?
Before you fire up your favorite Amiga software in the emulator, please DO READ the README file! It will save you (and me) lots of wasted time, I guarantee.
The very first thing I have to mention is that although I had done my best I was not able to finish implementing all the planned instructions. We are very close, according to the statistics 95.09% of the instructions (368 out of 387) are done. The reason is quite simple: the recently implemented instructions were the most complex ones. Well, you know this is exactly why you must not procrastinatethe hardest part of the job just because it makes you nervous even simply thinking about it... I have spent days on implementing BFINS and the exception handling for division by zero and I am still not convinced that it worth the effort. Anyway...
The following instructions are still emulated by the interpretive:
long versions of the division and multiplication instructions (DIVU.L/DIVS.L, MULU.L/MULS.L);
compare against bounds instructions (CMP2);
all the decimal data handling instructions (ABCD, SBCD, NBCD, PACK, UNPK).
The comparison and the decimal data handling is not that important, but the long division-multiplication are used quite often. So that is sill a sore point, yet I have decided that I will release the beta without these instructions to get some feedback. The missing instructions will be implemented soon, probably in the next beta release.
What is new in the sources?
Fixes and more
Since my last update I have managed to complete some more instructions and lots of bug fixes (thanks to Philippe Ferrucci and Davide Palombo, who insisted to demonstrate the JIT compiling at Alchimie and Pianeta Amiga shows, so I had to fix the most obvious bugs). I don't want to bore you with the details regarding the current changes, have a look at this update if you are interested.
Another important change was: I have merged the final sources for E-UAE 0.8.29 over my changes. Many thanks to Michael Trebilcock (MickJT) for driving my attention to the fact that I was using an outdated source version (0.8.29-WIP4) instead of the latest from the CVS (dated to 20/08/2008). For the changes please have a look at these two updates: original source, fix for audio.
The LED (round#2)
Philippe Ferrucci pointed out that sometimes it is hard to tell whether the JIT is available and working or not, in spite of the already available JIT LED. He suggested that the LED might also indicate other states of the JIT compiling, and I had found that a really useful idea. Now, you can identify three distinct states of the JIT compiling from the LED colors: 1. Blinking green with "JIT" text on it: JIT compiling is active and the compiled code is executed. The level of green shows you how active is the JIT compiled code compared to the interpretive-executed. (Same as before.)
2. Solid red with "JIT" text on it: the JIT compiling was set up, but the processor cache is turned off by the currently running software in the emulator, JIT compiling is not done while the cache is not turned on.
3. Solid black without "JIT" text on it: due to the emulator configuration the JIT compiling is not available. Either no code cache was set up or specified processor type does not support the processor cache.
Some help needed
Unfortunately, I have no idea how to compile the sources for other platforms than AmigaOS4. If you feel like you know enough about how to compile these sources please get in touch with me. I am looking for MorphOS, MacOSX PPC, Linux PPC versions especially, but any other supported platforms are welcome. (Thunder? Tobias? Mike? :) If you feel like there is a bug and you want to report it badly then please DO READ the How to report a bug section from the README before you jump on your mail client. Thanks.
It is a good start for a year, isn't it? I hope I can keep up and finally you can enjoy the benefits of the JIT compiling on your PowerPC machine.