Clang ALHP Repo(s)? #75
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#75
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Would work be considered for a Clang branch of the ALHP repos?
Not saying that this wouldn't be possible, but i think it would be a hell of a work to make the packages build with clang/llvm for lto, this require to modify each pkgbuild.
Even tho it could be automated, it @anonfunc that need to see this
This would be awesome to see!
Clang can only be used if you set gcc as fallback. I would be suyprised if more than 25% of all arch packages fully compile with clang. I would personally only look into it once the main compiler chain has been completly finalized. And even then it's debatable.
Kind of similar to #92 which asks for Polly which would also require LLVM/Clang.