Hey folks,
LLVM is fairly large, tons of contributors and what not. clang is one subset for LLVM.
I have been using gcc for many years, on linux - almost 20 years by now or so.
I know that we can also use clang. I tried it several times and it seems to work very
well. But I don't have as much experience with clang, as opposed to gcc.
I would like to systematically test compiling via clang for everything, including the
linux kernel. Ideally I'd just love to be able to use e. g.
And hope that this would suffice. But some programs may not work and what not.
Would it be possible for you guys to add some document or so, or perhaps on the
wiki, that can showcase some statistics, for compiling via clang?
For instance, for 3000 most used software projects on linux, if all of them can be
compiled via gcc, how many of these can be compiled via clang? Basically I'd
love to have some verifiable information as to how useful clang really is. Ideally
perhaps in an automated manner, similar to debian's reproducible build system.
Something we external users could also look up.
I am not sure how to best enable this, perhaps as a starter we can keep this
very simple, just a paragraph somewhere about experiences from more knowledgable
people having used clang for years? And ieally this could be stored in a documentat
in the long run; guess it may be useful to store it here in the github issue tracker
too.
I also think you guys want to keep the issue tracker clean, so perhaps this issue
request for documentation for clang, in actual real world use scenarios, could
remain open for one week from now on? And then it can be closed. (Not sure if
github allows auto-closing but I think one week may be a good compromise,
so that open issues like this here do not stay open for too long.)
At any rate, thank you for reading and potentially considering the request here.
It aims primarily to get more people to understand how to compile via
clang consistently. (Before I wrote this here, I saw a page about compiling the
linux kernel via clang, but they also made use of many additional environment
variables, which I found was a bit strange. For instance, can people build a
complete linux system via clang + musl? Does binutils, coreutils etc... work on
such a system? Right now I don't know and I think many other people don't
know either.)
Hey folks,
LLVM is fairly large, tons of contributors and what not. clang is one subset for LLVM.
I have been using gcc for many years, on linux - almost 20 years by now or so.
I know that we can also use clang. I tried it several times and it seems to work very
well. But I don't have as much experience with clang, as opposed to gcc.
I would like to systematically test compiling via clang for everything, including the
linux kernel. Ideally I'd just love to be able to use e. g.
And hope that this would suffice. But some programs may not work and what not.
Would it be possible for you guys to add some document or so, or perhaps on the
wiki, that can showcase some statistics, for compiling via clang?
For instance, for 3000 most used software projects on linux, if all of them can be
compiled via gcc, how many of these can be compiled via clang? Basically I'd
love to have some verifiable information as to how useful clang really is. Ideally
perhaps in an automated manner, similar to debian's reproducible build system.
Something we external users could also look up.
I am not sure how to best enable this, perhaps as a starter we can keep this
very simple, just a paragraph somewhere about experiences from more knowledgable
people having used clang for years? And ieally this could be stored in a documentat
in the long run; guess it may be useful to store it here in the github issue tracker
too.
I also think you guys want to keep the issue tracker clean, so perhaps this issue
request for documentation for clang, in actual real world use scenarios, could
remain open for one week from now on? And then it can be closed. (Not sure if
github allows auto-closing but I think one week may be a good compromise,
so that open issues like this here do not stay open for too long.)
At any rate, thank you for reading and potentially considering the request here.
It aims primarily to get more people to understand how to compile via
clang consistently. (Before I wrote this here, I saw a page about compiling the
linux kernel via clang, but they also made use of many additional environment
variables, which I found was a bit strange. For instance, can people build a
complete linux system via clang + musl? Does binutils, coreutils etc... work on
such a system? Right now I don't know and I think many other people don't
know either.)