Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Compilers & Toolchains primarily focuses on GCC and LLVM, but may include specific items from binutils, golang or other compilers. 


Our WG does not have a recurring meeting; instead we try to handle RISE specific items via email and the project specific items in the project related meetings (noted below).

Resources

GCC

There is already a call Tuesday morning US time where engineers from relevant companies sync on patch status, coordinate on projects spanning multiple organizations, etc.  That call is primarily GCC focused:

Call link:

https://meetus02web.googlezoom.com/gsf-dchk-ijn?authuser=0&hs=122Patchwork Instance:us/j/89248678441?pwd=QjRCWWFZMmFnNVZNdGVDL0xrUUYzQT09

Patchwork Instance (we focus on patches with RISC-V in their subject line, so filter on that).

https://www.google.com/url?q=https://patchwork.sourceware.org/project/gcc/list/?q%3Drisc-v&sa=D&source=calendar&ust=1684855869591441&usg=AOvVaw1uV11mIRIDJRQRY0fSjra_

Meeting notes:

https://docs.google.com/document/d/1bW2jgRmhYdHz7oVw5EUcXVAv4_cfuBaZ5bhVG1pUnIo/edit#heading=h.7d43oinlp937

My sense is that for GCC/binutils we’ll largely be bubbling up status from that meeting to RISE.Coordination branch:

https://gcc.gnu.org/git/?p%3Dgcc.git;a%3Dshortlog;h%3Drefs/vendors/riscv/heads/gcc-13-with-riscv-opts

LLVM

There is an LLVM RISC-V sync call as well.  I have not been able to attend, so I’m not as up-to-speed on the LLVM side.  The call is every other week.  The next iteration is May 25, 2023, 8am Pacific time.

...

https://www.google.com/url?q=https://llvm.org/docs/CodeOfConduct.html).&sa=D&source=calendar&usd=2&usg=AOvVaw3qHCIjgVr7sD33J24MqSwG

Meeting notes:

https://www.google.com/url?q=https://docs.google.com/document/d/1G3ocHm2zE6AYTS2N3_3w2UxFnSEyKkcF57siLWe-NVs/edit%23&sa=D&source=calendar&usd=2&usg=AOvVaw3bpjSGw4A5A7PrzhwiddK1

Zoom link:

https://us06web.zoom.us/j/86813490775?pwd=RUxreUtGR0Jsb2M0dzFQR3VMUndYdz09

...