SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I know this has been asked before regarding if Slackware could or would switch to LLVM-Clang at some point, but my question is a bit less inclined to when to more of this:
From reading up on LLVM-Clang's capabilities in comparison to GCC, would, and is it even possible to build Slackware, or even rebuild Slackware from the ground-up using only LLVM-Clang? And if so, would there be any benefits, with list and examples, but if not, what are the shortfalls and problems of this approach?
I know this has been asked before regarding if Slackware could or would switch to LLVM-Clang at some point, but my question is a bit less inclined to when to more of this:
From reading up on LLVM-Clang's capabilities in comparison to GCC, would, and is it even possible to build Slackware, or even rebuild Slackware from the ground-up using only LLVM-Clang? And if so, would there be any benefits, with list and examples, but if not, what are the shortfalls and problems of this approach?
I'll try to summarize: Yes, it would be possible, but not without some patches (and some of those patches would have to be applied to Clang). The patches for this generally don't exist yet -- so figuring them out would be part of the exercise. Until someone does this, it's not possible to say with any certainty whether the resulting binaries would work better, but I'd tend to think that there would not be a huge difference. Since most people are currently compiling with gcc, compiling with Clang is not as well tested, and is likely (at this time) to be less reliable.
One small example -- I got a report than since recompiling LLVM/Clang using Clang, it quit working on a Pentium III machine. So it's possible that Clang is less able to control itself in terms of retaining compatibility on older x86 CPUs.
Thanks for the insight into this Patrick. Much appreciated.
I hadn't heard about that x86 Pentium III issue, but as with anything like that, various factors could have been involved.
It would be interesting to see how it would affect non-legacy builds like x86-64 though as compatibility with Pentium III is less than fickle a worry.
As far as patches go, I know FreeBSD has been keeping a good update on their ports packages recently, perhaps a study of their work can land some insights into a full work-over of LLVM/Clang usage.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.