Modular code generation?

[SamuraiCrow]

Hello! If you've been following the QBE mailing list, you probably know that I'm trying to make a 32-bit code generator library based on LibQBE. Nowadays, 32-bit systems are frowned upon as 'toy' computers but only because some software is to big to fit in the given address space.

Since my existing code generators are written in self-hosted AmigaE rather than C11, I'm hoping to make the code generators and optimizer a separate library from each other and the ABI separate also, both for code reuse purposes and cross-language maintainability.

My request is: Could the final code-generators (as a minimum) and optionally, the ABI runtime generation be made into separate .c files from the main optimizer?

I do know some Python and am looking at the script. I'd just like to know if there are any "gotchas" to look out for.

[SamuraiCrow]

I've almost finished a preliminary step of getting QBE to link from static linker libraries instead of directly from object files. All that remains from that first step is making main.c use just one target at a time.

[SamuraiCrow]

Initial success building QBE has been accomplished by grouping objects into linker libs. The executable is 100k smaller when using only the default backend.