Hi Bruce,
You can add -march options in the compiler switches command line area at the top right of each compiler window.
I'm not sure about how to configure compiler-explorer to show instruction words in the output. There is a global config option for objdump which I've not set. I have a feeling from looking at the config examples that I might need to point it at a shell script that does file and invokes the architecture specific objdump as it is a global. Matt's AWS example config points at a special objdump.
The default config btw is to just locate the compilers on the host machine. I had to look at some of Matt's AWS config examples to figure out how to get it working with multiple architectures. e.g. using the compiler group feature.
It also requires a google API key to get the URL shortener to work which took me a while to figure out as that is also off by default. I had to enable the API and configure an API key in the Google Developer console.
There is also an LD_PRELOAD compiler wrapper that is off by default which is likely there to harden the setup for the cloud. I thought I switched on that option.
It was quite easy to set up. I guess adding ARM32 and ARM64 might be possible... it took ages to upload the toolchain and the machine is too meagre to actually build a toolchain.
It would be kinda nice to have on the
riscv.org domain although it likely needs to be sandboxed from other apps. The only thing I have on that box is an SSL proxy to enable https on GitHub pages (as GitHub don't seem to have letsencrypt configured if you use a custom domain for GitHub pages). I reused the apache https proxy config as by default node binds to an ephemeral port serving http. Secure compiler snippets. :-D
Michael
Sent from my iPhone