Skip to content

Add compiler: IDO 5.3 + MIPSPro C++ 6.2 from ido-static-recomp - #99

Open
queueRAM wants to merge 1 commit into
decompme:mainfrom
queueRAM:add_ido5.3_mipspro6.2
Open

queueRAM wants to merge 1 commit into
decompme:mainfrom
queueRAM:add_ido5.3_mipspro6.2

Conversation

@queueRAM

@queueRAM queueRAM commented Nov 16, 2026 •

Copy link
Copy Markdown
  • Add ido5.3_mipspro6.2: IDO 5.3 + MIPSPro C++ 6.2

- Add ido5.3_mipspro6.2: IDO 5.3 + MIPSPro C++ 6.2
@queueRAM
queueRAM force-pushed the add_ido5.3_mipspro6.2 branch from 839ea5e to 383d839 Compare November 17, 2026 00:06
@queueRAM queueRAM changed the title Add IDO 5.3 + MIPSPro 6.2 compiler Add compiler: IDO 5.3 + MIPSPro C++ 6.2 from ido-static-recomp Nov 17, 2026
@queueRAM
queueRAM marked this pull request as ready for review November 17, 2026 00:07
@mkst

mkst commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Why not update the existing ido5.3 recomp and then use that as the base compiler in decomp.me?

edit example of using a base_compiler in decomp.me : https://github.com/decompme/decomp.me/blob/main/cromper/cromper/compilers.py#L959

@queueRAM

Copy link
Copy Markdown
Author

Why not update the existing ido5.3 recomp and then use that as the base compiler in decomp.me?

Good question. In this instance, it is MIPSPro 6.2 that is providing the C++ frontend. One could also install MIPSPro 6.0, 6.1, 7.0, or 7.1 and still rely on IDO 5.3 for codegen. So if all that is ever needed is 6.2, then I think we could just update IDO 5.3 to use it for C++, but if other variations of MIPSPro exist, then I think it would be more appropriate to have its own compiler configuration. Open to feedback though since I really don't know what I'm doing.

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

Successfully merging this pull request may close these issues.

2 participants