Hi all,
I've kicked off a documentation initiative to try to better specify
the command-line switches and behaviour of RISC-V toolchains that aim
to be compatible with GCC (such as Clang). The aim of this is
three-fold:
* Aid the RISC-V LLVM/Clang effort by better specifying the expected behaviour
* Provide a place where RISC-V toolchain implementers can plan how to
evolve the supported switches
Further down the line, I'd also like us to more actively seek feedback
from upstream GCC and Clang communities. I know that command line
options and related issues may seem a little tedious, but it's
important we get things right and make choices that meet the upstream
norms.
I'm particularly interested in ensuring there are clear guidelines on
the preferred way of exposing custom vendor-specific extensions.
Having vendor-specific toolchains is inevitable, but I'd hate for them
to end up with arbitrarily different command line interfaces just due
to a lack of communication.
See <
https://github.com/lowRISC/riscv-toolchain-conventions> for the
current document as well as the issues page
<
https://github.com/lowRISC/riscv-toolchain-conventions/issues>. I'd
really welcome help in fleshing the document out, and proposals for
addressing the identified issues.
Are people happy for this to be moved under the riscv github organisation?
Thanks,
Alex Bradbury, lowRISC CIC