The goal of maspsx is to facilitate the replacement of the combination of ASPSX.EXE + psyq-obj-parser when attempting to generate byte-perfect ELF objects.

maspsx takes the assembly code output of gcc and massages it such that it can be assembled via GNU as to the equivalent object as what the original PSYQ SDK would create.

ASPSX does not appear to do very much in terms of code optimisation, therefore the belief is that this will be a straightforward process.

There are a number of reasons why using maspsx with GNU as is preferable to the original toolchain:

• No need to run 16-bit DOS or 32-bit Windows applications
  • Native, vanilla, gcc versions make dosemu2 and wine unnecessary.
• Decomp tooling expects ELF objects
• Support for line numbers in diff!
  • Pass -gcoff to gcc to get line numbers in asm-differ

maspsx supports the following arguments:

EXPERIMENTAL There are slight nuances in behaviour across ASPSX versions. In order to emulate the correct behaviour, pass the ASPSX version to maspsx, e.g. --aspsx-version=2.78.

The default behaviour of maspsx is to write the output to stdout, by passing --run-assembler, maspsx will run mipsel-linux-gnu-as directly.

If mipsel-linux-gnu-as isn't on your path, or you want to use a different assembler (e.g. mips-linux-gnu-as), specify the full path here.

Current understanding is that -G0 needs to be passed to GNU as in order to get correct behaviour. If you need to pass a non-zero value for -G to the GNU assembler, use this flag.

If you need maspsx to expand div/divu and rem/remu ops, pass --expand-div to maspsx. There is already handling for partial div expansion (i.e. where -0 was passed to ASPSX.EXE).

Get maspsx to add an include "macro.inc" statement to the output.

Put any common symbols (in C, this means non-static global variables without an initializer) in the .comm section (which is the default ccpsx behaviour).

Also put .lcomm-declared symbols (in C, this means static variables without an initializer) in the .comm section. This can be convenient with games using non-zero -G in situations where a variable needs to be marked static to get code generation to match, but you don't want to migrate .sdata/.sbss to that .c file yet. NOTE: This also makes the symbols global (unlike regular static behaviour).

EXPERIMENTAL If your project uses $gp, maspsx needs to be explicitly passed a non-zero value for -G.

Whenever compiling with non-zero -G value, some versions of gcc reorder all functions to appear after data definitions in the output assembly. Unfortunately, this also causes functions to be placed after __asm__ statements, thus breaking the usual implementation of the INCLUDE_ASM macro.

This can be worked around with maspsx by wrapping each __asm__ statement in a function whose name starts with __maspsx_include_asm_hack, and appending # maspsx-keep to each line of the __asm__ statement. Thus a working version of INCLUDE_ASM would look like:

#define INCLUDE_ASM(FOLDER, NAME) \
    void __maspsx_include_asm_hack_##NAME() { \
        __asm__( \
            ".text # maspsx-keep \n" \
            "\t.align\t2 # maspsx-keep\n" \
            "\t.set noreorder # maspsx-keep\n" \
            "\t.set noat # maspsx-keep\n" \
            ".include \""FOLDER"/"#NAME".s\" # maspsx-keep\n" \
            "\t.set reorder # maspsx-keep\n" \
            "\t.set at # maspsx-keep\n" \
        ); \
    }

Projects that use maspsx include:

• Castlevania: Symphony of the Night Decompilation
• open-ribbon
• Evo's Space Adventures
• Croc: Legend of the Gobbos
• Legacy of Kain: Soul Reaver
• Silent Hill
• Rayman 1
• Spyro The Dragon
• MediEvil 1

This project is a work-in-progress. If you encounter scenarios where maspsx output differs from the original PSYQ toolchain please create a GitHub Issue - ideally with a link to a decomp.me scratch that demonstrates the problem.