doesn't seem to compile with clang

[tnuha]

My issue in #33 was my choice of compiler. Some users may be more familiar with LLVM infrastructure than gnu, so allowing for selection of different compilers might be helpful. LLVM may also enable instruction extensions to be transparent to user code via intrinsic functions.

[KaivalyaD]

Please let me know if I understand you correctly:

1. You're confirming issue #33 was because you were using Clang instead of a GNU compiler when compiling Arches (the simulator).
2. You would like to use Clang because you want to be able to add instruction extensions when compiling RISC-V kernels (the simulated).

I'll try to look into what caused 1. Can you share details of the compiler you used?

For 2, I see why you might want to be able to do that. We are currently proposing an entirely different approach to adding custom instructions using the .insn assembler dot-directive. While we understand that this method does not lead to a nice and readable code, or shows up as a human-readable mnemonic in object dumps, it has the great advantage of eliminating compiler compilation entirely. This is best-suited for the course. You may, if you want, have a look at acac330 (not yet merged with master).

That said, I highly doubt that using Clang for compiling the kernels should pose any issue. As far as Arches is concerned, it feeds on the compiled machine code. Feel free to use any compiler you want for the kernels, and in case you find any troubles there, please post an issue!

Thanks a lot for helping improve Arches!

[tnuha]

I believe for 1 you should be able to hit this issue with any clang version. I have this problem on Apple clang version 21.0.0 (clang-2100.0.123.102) among others (not all Apple)

[KaivalyaD]

@GauravAB92 can you try building Arches with the said compiler on your macbook?