3 ms·

The support in gcc and clang for RISC-V is so mature at this point that there are binaries and ports in distributions like Debian, arch, and windows (Msys), *BS

The support in gcc and clang for RISC-V is so mature at this point that there are binaries and ports in distributions like Debian, arch, and windows (Msys), *BSD. It would probably be more convenient and reproducible to start with those. > I consider this repo as an "exploded container" designed to be deployed in a VM to put your code in and get your binaries out. Only after compiling the whole thing. And it’s not like this does anything special to enforce reproducibility. On that note there are preexisting docker containers.

bayindirh 4y ago
Considering this repository started its life in 2014, maybe here's the place where all started, and helped incubating said containers and distro support over the years? Considering it has 858 forks incl. by corporations like WD Semi and SiFive, I think I'm not too far off in my guess.
- riceart 4y ago
  No. gcc and clang development do not occur on github and likely never will. Gcc didn’t even use git until relatively recently (not in 2014). You can go look up the mailing list archives - this repo predates nothing. > helped incubating said containers and distro support over the years? Tool chain build scripts for gcc and clang have existed for as nearly as long as the respective projects have been around - which in the case of gcc is over 30 years. Also see https://crosstool-ng.github.io/ https://crosstool-ng.github.io/ Distros like Debian have been packaging cross compilers for decades with their own tooling, long before 2014. MSYS has existed for I can’t remember (long before 2014). As someone below said - this is a “very solved problem”. Not that this repo isn’t useful - but I think posted here out of context clearly it is conveying the impression that it is bringing something novel to RISC-V which isn’t the case.

3 ms·

The support in gcc and clang for RISC-V is so mature at this point that there are binaries and ports in distributions like Debian, arch, and windows (Msys), *BS

by riceart 4y ago

bayindirh 4y ago
Considering this repository started its life in 2014, maybe here's the place where all started, and helped incubating said containers and distro support over the years? Considering it has 858 forks incl. by corporations like WD Semi and SiFive, I think I'm not too far off in my guess.
- riceart 4y ago
  No. gcc and clang development do not occur on github and likely never will. Gcc didn’t even use git until relatively recently (not in 2014). You can go look up the mailing list archives - this repo predates nothing. > helped incubating said containers and distro support over the years? Tool chain build scripts for gcc and clang have existed for as nearly as long as the respective projects have been around - which in the case of gcc is over 30 years. Also see https://crosstool-ng.github.io/ https://crosstool-ng.github.io/ Distros like Debian have been packaging cross compilers for decades with their own tooling, long before 2014. MSYS has existed for I can’t remember (long before 2014). As someone below said - this is a “very solved problem”. Not that this repo isn’t useful - but I think posted here out of context clearly it is conveying the impression that it is bringing something novel to RISC-V which isn’t the case.