Search results

The faster memory access and larger cache of the OMAP4 might improve performance. Currently there is limited multi-thread support so there would be little to gain from dual cores. It would be possible to do graphics or audio on the second CPU, but the current code is not written that way. I...

There are a few improvements in the new version, but the overall compatibility rate hasn't changed much. The reason for moving to the new version would be to use future plugins that are designed for v2.0. There isn't any immediate benefit, it's more of a long-term goal.

It's doable, but it would need cop2 support and a psx memory map, at least. It doesn't look like he made much progress on that.

psx4m clearly uses code from zodttd, but I'm not sure how old it is. Many of the files are dated July 2010 though. The dynarec that it uses appears to be the one that hlide and zodttd did. There is an older version of the dynarec that I wrote in there, but it doesn't appear to actually use it.

http://maemo.org/packages/source/view/fremantle_extras-devel_free_source/psx4m/0.4.3-1/ Is that actually using the dynarec that it appears to be using? That code looks very familiar... :)

They're taking orders, to be delivered whenever Circuitco finishes making them.

Yeah, there isn't much left to do on the dynarec. If I get bug reports, I'll investigate, but I've fixed all the problems that I know of.

Beyond the bugfixes that I just posted, I have no updates planned for the dynamic recompiler. Every game that I've tested that worked on the old x86 version works on ARM. At some point I will probably look into merging the dynarec with 1.99.3. I haven't done anything on that yet, so if...

http://bunnitude.com/ari64/mupen64plus-arm-20101026.tar.gz Changes since 20100929: - Fixed i-cache invalidation bug (random crashes) - Fixed register writeback when splitting code blocks to accommodate changes in vitrual memory mapping

Well I guess you could buy me a pandaboard or a new computer or something ;) Last I tried, it crashed glN64, and was glitchy in rice video. I haven't really looked into it.

It gives a detailed description of the various power management modes, but no estimates of total power consumption. It's a huge document, so maybe I missed something. I was a little surprised by this warning: Maybe they're just being paranoid, but the beagleboard does not get that hot. It...

Early reports on the PandaBoard suggest it has some power management issues. Apparently it draws too much current to be powered by USB, and the recommended power supply is 20 watts. I don't know how much power the OMAP4 really needs, but it may be awhile before there's a drop-in replacement...

I haven't heard from Adventus. He's probably waiting for a Pandora, like the rest of us.

Yes. The speedup was associated with generating VFP instructions in the dynamic recompiler. It only affects the CPU emulation, not graphics or sound. I'm working on another update, since I found two bugs (crashes) in the last release.

Yes, it seems that it only inlines functions below a certain size, so it does this less than I thought it did.

It'll do it even if the function is global. Hopefully the function doesn't get called from any other linked object file, but gcc compiles the function independently just in case it does. This dead code contributes to the code bloat associated with -O3. I'm not sure if the linker has any way...

LOL, I think that was sarcasm. If you put things into functions that are only called from one place, then the optimizer can improve it by inlining. (And gcc -O3 will inline all functions that are only called from one place.) The register and volatile stuff was just silly.

Alignment does make a difference on cortex-a8, however GCC 4.3.3 never aligns code on ARM, even if you specify -O3 and -mcpu=cortex-a8.

What makes you think that Mupen64plus was compiled with something other than what's in the Makefile (-O3)? I'd love to see what benchmarks you used to measure a considerable (10%ish) speed increase.

The config files were exactly the same as in mupen64plus v1.5.