Add ssb_ido5.3 and ssb_ido7.1 - #77
Conversation
* Add ido5.2 * Add ido5.2 Dockerfile * Generate ido5.2 Dockerfile with template.py --------- Co-authored-by: LLONSIT <LLONSIT@users.noreply.github.com>
Co-authored-by: sbird <sbird@no.tld>
* Add wcc10.0a * Update values.yaml Co-authored-by: Mark Street <22226349+mkst@users.noreply.github.com> * Regenerate wcc10.0a Dockerfile --------- Co-authored-by: Mark Street <22226349+mkst@users.noreply.github.com>
Package the default-off-compatible agbcc build used by fireemblem8j so decomp.me can compile scratches with the project-local -mjp-promote target flag. Co-authored-by: laqieer <laqieer@126.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 990a295e-cc42-4f64-8303-1599ab35abfb Co-authored-by: GitHub Copilot <223556219+Copilot@users.noreply.github.com>
|
What's this? And maybe |
Well, it would be nice to test this weird experiment with other functions from that overlay. We know this compiler mess could be real because of func_ovl8_803781A4, since the only way to match this function is by using an old IDO frontend that generates a jump table with a four-case switch. We are not really sure if they mixed the old C frontend with 5.3 or 7.1, so that's why I added both, to test all possible cases. |
|
Not super keen to add a compiler to the site purely for experimentation, feel like that could be done offline, and once you're confident it's the right thing, then we add it.. or if we can do like I said earlier, where we add additional binaries to ido5.3 and then you pick via runtime flags? |
Well, my intention is to let others try this, since I think this compiler might be a little bit too difficult to set up because of qemu-irix
Do you mean invoke the IRIX 4 binaries from recomp? |
|
https://discord.com/channels/601153657966428193/720795286557163543/1532825142730948639 Suggests we could have a |
Well, the thing that makes this specific for SSB is that the original developer used only one COFF binary ( |
No description provided.