Re: [hatari-devel] New version of WinUAE's cpu core

[Nicolas Pomarède <npomarede@xxxxxxxxxxxx>]

Le 23/11/2014 23:17, Eero Tamminen a écrit :
> Hi,
>
> On sunnuntai 23 marraskuu 2014, Nicolas Pomarède wrote:
> > > What features in existing cores are still missing from the new core?
> >
> > Don't see what you mean. Existing core is much less precise, the new
> > core doesn't necessarily requires more options in the UI, it's much more
> > some internal improvements with more or less the same API.
>
> After Laurent added WinUAE core to Hatari, it was for a long
> while missing integration (at least) to several debugging and
> tracing features, which were already provided by old-uae core.
>
> todo.txt is still listing two items for it: [1]
>          - Add Exception debugging support
>          - Instead of calling Reset_Cold()/m68k_reset()/uae_reset()
>            directly from newcpu.c, show user a notice (dialog)
>            about what happened and let user do the reboot
>            (see "Emulation reset, old-UAE vs. WinUAE core" mail-thread)
>
> Has your new WinUAE port integrated all such features already?
>
>
> 	- Eero
>
> [1] I think first one was actually already done?

For now, I didn't check any pending todo's for WinUAE. 1st step to just 
run the new core version was a really long task, requiring to test a lot 
of cpu / accuracy level combinations. At start, nothing really worked at 
all, even in 68000 mode.

All options that were in Hatari 1.8 have normally been ported to this 
new version. If not, let me know, but nothing new was added for now.

My plans are :
 - sync with latest winuae's beta. I included some of the changes, as I 
also reported some bugs to winuae, but not all of them.
 - improve cycles accuracy for 68000 and 68030, requires to check some 
timings sensitive demos for example.
 - add TT ram support and more flexibility to the 24 bit adressing mode

Once I reach this, we can consider this new cpu core is stable enough 
and we can add new features.

Nicolas