RISC-V toolchain conventions: documenting and standardising toolchain behaviour across GCC, Clang, and others

130 views
Skip to first unread message

Alex Bradbury

unread,
Oct 25, 2017, 10:29:03 AM10/25/17
to RISC-V SW Dev
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

Andrew Waterman

unread,
Oct 25, 2017, 2:22:05 PM10/25/17
to Alex Bradbury, RISC-V SW Dev
Thanks Alex. It would be frustrating indeed if the command-line
interfaces diverged in minor ways for lack of coordination. Makes
sense to move this to risc-v github.
> --
> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
> To post to this group, send email to sw-...@groups.riscv.org.
> Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CA%2BwH295pZDTEwfm32Kkj4jYwwivhe1AudF0tJPZAyeEbzsNdDg%40mail.gmail.com.

Rick O'Connor

unread,
Oct 25, 2017, 2:26:25 PM10/25/17
to Andrew Waterman, Alex Bradbury, RISC-V SW Dev
Thanks for the initiative Alex!  Agreed, it makes sense for this to be under the RISC-V Foundation github repo.

Andrew, can you look after (or have someone look after) moving this over?
Cheers,
Rick

Rick O'Connor
Executive Director
RISC-V Foundation

> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.
--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.

To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

Alex Bradbury

unread,
Oct 25, 2017, 2:40:52 PM10/25/17
to Andrew Waterman, RISC-V SW Dev
On 25 October 2017 at 19:21, Andrew Waterman <and...@sifive.com> wrote:
> Thanks Alex. It would be frustrating indeed if the command-line
> interfaces diverged in minor ways for lack of coordination. Makes
> sense to move this to risc-v github.

Andrew, Rick - thanks. It looks like I have sufficient privileges to
initiate the move so I've gone ahead and done so. Old URLs will
redirect, but you can now also head directly to
https://github.com/riscv/riscv-toolchain-conventions.

Best,

Alex

Rick O'Connor

unread,
Oct 25, 2017, 3:26:08 PM10/25/17
to Alex Bradbury, Andrew Waterman, RISC-V SW Dev
Great!  Thank you Alex.
Rick

Rick O'Connor
Executive Director
RISC-V Foundation

--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.

To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

David Chisnall

unread,
Oct 26, 2017, 6:48:38 AM10/26/17
to Alex Bradbury, RISC-V SW Dev
Thank you,

Anyone who has suffered with vendor toolchains for MIPS, anything provided by IBM, or with pre-ARMv7 toolchains for ARM, will understand the pain that not doing this properly can cause.

David
> --
> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
> To post to this group, send email to sw-...@groups.riscv.org.
> Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CA%2BwH295pZDTEwfm32Kkj4jYwwivhe1AudF0tJPZAyeEbzsNdDg%40mail.gmail.com.

Reply all
Reply to author
Forward
0 new messages