Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remaining nucode issues wrt. emulator upcode #416

Open
Wuerfel21 opened this issue Sep 14, 2023 · 1 comment
Open

Remaining nucode issues wrt. emulator upcode #416

Wuerfel21 opened this issue Sep 14, 2023 · 1 comment

Comments

@Wuerfel21
Copy link
Contributor

To follow up to P2LF, the stack smash fix does indeed work, but there's some other issues now.

MegaYume cannot currently compile upper in Nu mode because it can't seem to handle arrays in inline asm properly. This is actually an issue with the usbnew driver, so fairly critical I guess. The keystate function needs a size-2 array to block read into to make sure that it gets an atomic snapshot of the keyboard report.

NeoYume compiles, but the menu behaves oddly and freezes for short periods of time. Also, some games will hang after loading 5888k of data (23 dots). Sometimes this also corrupts the screen. No idea what distinguishes the working from the broken gamedb entries. Also, when it works it's really slow on some file types, but that's expected. Could probably rewrite all of the file types in inline asm like LOAD_CROM is.

It's bedtime again (was busy today), so not looking into debugging that one right now. Also here's some hope to finding your lost AV board.

@Wuerfel21
Copy link
Contributor Author

usbnew compile error is fixed now.

Current status:

  • Megayume works now (including SRAM backup)
  • both programs have freezes during menu scrolling. Megayume is less affected, might be different problem - MY loads file contents while scrolling, does opening and closing files create GC objects that are too slow to collect in nu mode? (meanwhile NY's menu doesn't do any library calls)
  • NeoYume still mega busted and likes to crash at that exact 5888k point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant