Conversation

Notices

1. Embed this notice
   翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 20-May-2024 17:33:31 JST 翠星石

   in reply to

   • Dushman
   @dushman Clang+LLVM is NOT superior to GCC, rather it's the other way round.
   This is a fact.
   
   The most important thing when it comes to software is the license, followed by functionality.
   
   GCC is licensed under the GPLv3-or-later, which is a freedom-defending license and ensure that the compiler is always free.
   
   Meanwhile, clang is licensed under the pushover Apache 2.0 with further exceptions, which means that proprietary version are allowed and many of those do exist - all taking the users freedom.
   
   
   When it comes to functionality, GCC supports all the GNU C features, supports more architectures and compiles in a reasonable time, with a reasonable amount of memory (as the limited subset of sepples allowed limits the drawbacks of sepples).
   
   Sure Clang does the equivalent of -funroll-loops when compiling with -O3, meaning it often produces faster code when it comes to benchmarks, but when it comes to the important things like compiling GNU software, it produces worse binaries.
   • snacks likes this.
   • Embed this notice
     Dushman (dushman@den.raccoon.quest)'s status on Monday, 20-May-2024 17:33:35 JST Dushman

     clang is superior to gcc
     this is a fact

     snacks repeated this.
   • Embed this notice
     munir (munir@fedi.munir.tokyo)'s status on Monday, 20-May-2024 18:39:38 JST munir

     in reply to

     • EdBoatConnoisseur
     • Dushman
     @EdBoatConnoisseur @dushman @Suiseiseki Clang gives way better errors so idk
   • Embed this notice
     EdBoatConnoisseur (edboatconnoisseur@poa.st)'s status on Monday, 20-May-2024 18:39:39 JST EdBoatConnoisseur

     in reply to

     • Dushman

     @Suiseiseki @dushman the only functional advantage of clang is when you are already working with a llvm stack and you are not working just with C.

     the other advantage is that you just need a frontend to convert whatever syntax you wish into the llvm internal code language and then u can have it spitting out from any backend.

     an example usage of the llvm stack would be stuff like jamulator.

     https://andrewkelley.me/post/jamulator.html