Thanks for posting the link. I wonder what improvements could be made regarding the reference to an executable compiled specifically for PA-Semi / X1000
On my SAM460ex if I don't set 'ppc.use_tbc=false' in .uaerc timebase is wrong calculated: .. E-UAE 0.8.29-PPCJITBETA02 Build date: Mar 9 2014 14:20:46 Found 0 joysticks Opening cfgfile '.uaerc'...okay. Error: directory 'OS3' not found unknown config entry: 'enable_jit=yes' Calibrating timebase... Timebase frequency: 296.143080 MHz ..
Setting such option I get: .. #uaeJIT E-UAE 0.8.29-PPCJITBETA02 Build date: Mar 9 2014 14:20:46 Found 0 joysticks Opening cfgfile '.uaerc'...okay. Error: directory 'OS3' not found unknown config entry: 'enable_jit=yes' EClock frequency:1155.000010 MHz ..
"executable compiled specifically for PA-Semi / X1000"
Do we have gcc that supports compiler optimizations for PA6T? Then... we need gcc that is aware of e5500 & e6500.
- Kimmo --------------------------PowerPC-Advantage------------------------ "PowerPC Operating Systems can use a microkernel architecture with all it�s advantages yet without the cost of slow context switches." - N. Blachford
Am I right in thinking that the GCC we have pre-dates the PA6t? I'm not sure anyone is maintaining GCC are they? We really need support for our flagship.... is the current GCC version in thr official GCC repisitory?
E-UAE JIT beta 2 detects sam440ep and skips calculating the timebase. MACHINETYPE_SAM460 isn't included in the SDK that Rachy built it with, but I think that can be worked around without updating the SDK, seeing as it's just a numerical value. I'll let him know.
enable_jit=yes
cpu_speed=max
cpu_type=68020
cpu_compatible=false
cpu_cycle_exact=false
blitter_cycle_exact=false
comp_optimize=no (see Known issues)
cachesize=8192 (or higher)
comp_constjump=yes
comp_trustbyte=indirect (see Known issues)
comp_trustword=indirect
comp_trustlong=indirect
cachesize=16384
cpu_type=68EC020/68881
#cpu_type=68040
# CPU compatibility (true is slower)
cpu_24bit_addressing=false
# CPU emulation speed
# real = approx A500 speed. max = CPU emulation will run as fast as it can
cpu_speed=max
# Amiga chipset to emulate
# Can be ocs, ecs or aga
Yes is strange thing about TimeBase frequence I don't know if this is calculated or if this what it reads from Timer.Device :-/
As for slow JIT preperformance, I think thats because of what I wrote before, but maybe there is some thing strange going on, whit Timer.device.
I'm not so shore anymore, should it not be 1800 Mhz on X1000? Or what is the correct value?
Yes the Picasso96 video modes will be faster then AGA modes, 1 to 1 emulation, instead of having to do planar to chunky concertion + cooper emulation on the palette while converting it into native videomode, or what ever it does.
I'm shore the AGA emulation is efficient, but not as efficient as native video modes.
Edited by LiveForIt on 2014/3/20 0:57:17
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Do you get the same frequency issue (66mhz) with beta 1, or with any other version of e-uae, when ppc.use_tbc is false? Is the frequency calculated correctly if you use the non-JIT versions of e-uae and ppc.use_tbc=true ? Try with the version that comes with RunInUAE.
I know that on my sam440ep-flex, in versions of e-uae PPC JIT prior to beta 2 (beta 2 specifically detects a sam440 or amigaone, but not 460/x1000), if I didn't have ppc.use_tbc=false, the frequency would be calculated wrong and the JIT would be much slower. In my experience it definitely affects the JIT speed.
Looks like a define will need to be made for X1000, but someone else will have to figure out what to do for that. You could probably hardcode a figure that assumes all X1000 CPUs are the same speed (which afaik is true for now).