Standardize the names of object files created by the popcorn compiler about popcorn-compiler HOT 5 CLOSED

I'm not opposed to the change, but the reason I chose to generate the ARM file without an extension was so that big monolithic build systems that expect a ".o" that directly corresponds to a ".c" wouldn't fail. However, we haven't gotten to the point where we're compiling these projects yet, so maybe it'd be a good idea to add these architecture extension for all files.

Ideally we'd just generate a fat object file, i.e., the object file would have data and text sections for all ISAs. However this probably requires a significant amount of linker/OS loader engineering.

from popcorn-compiler.

I see the point but the direct mapping .c -> .o, while being the case for ARM with the current Makefile, is not the case for x86 right?

from popcorn-compiler.

Correct. Basically, I just wanted to generate some .o file so that build systems wouldn't choke when the compiler didn't obey "-o" flags.

from popcorn-compiler.

Got it. If we really need to have a xxx.o file (without any architectural suffix in the name), maybe we could just make a copy of this file and name it xxx_arm.o, however it introduces some redundancy...

from popcorn-compiler.

I'm closing the issue, still I want to state that to overcome this I made a terrible hack around line 200 in the file Symbol.py in pyalign.

from popcorn-compiler.