3 ms·

Can TinyCC still compile the 5.x kernel without issues?

• rurban 4y ago
  No, this is being worked in. The goal should be a -Oboring optimizer without any broken optimizations and aggressive UB assumptions. Something neither gcc nor clang can provide.
• wrycoder 4y ago
  See bootstrapping.org
  • chexum 4y ago
    http://bootstrappable.org http://bootstrappable.org perhaps?
    • wrycoder 4y ago
      oops. Thanks! https://bootstrappable.org/ https://bootstrappable.org/ https://bootstrapping.miraheze.org/wiki/Mes https://bootstrapping.miraheze.org/wiki/Mes https://reproducible-builds.org/ https://reproducible-builds.org/ https://archive.fosdem.org/2021/schedule/event/gnumes/ https://archive.fosdem.org/2021/schedule/event/gnumes/
• sylware 4y ago
  you cannot, as linux code is using a lot of gcc/clang extensions stuff, namely this is some sort of C dialect, not really C. Almost at every new release of linux, "somebody" did manage to commit into its code the usage of new gcc/clang extensions. The right(TM) way would be to port linux to simple and lean C (like some simple C89 with benign bits of c99/c11): the price is some loss of performance which could be partially mitigated with an assembly port of critical fast-paths (I guess that would show on really loaded servers only). In the end, if RISC-V is a success, namely a world with a pertinent ISA without toxic IP tied to it (like x86/arm), then a full assembly port of linux would be more than interesting in order to rid it from compiler tantrums.
  • MuffinFlavored 4y ago
    > you cannot, as linux code is using a lot of gcc/clang extensions stuff Linux 5.x kernel that is, but not Linux 4.x kernel because that was tcc-compilable?