-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
ghc: silence error on non-x86_64 with clang #251447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems reasonable.
I have two questions:
pkgs/top-level/haskell-packages.nix? We already do this for a few of our compilers, if I recall correctly.pkgs/top-level/haskell-packages.nixto something earlier than 16, then the changes in this PR won't negatively effect anything, right? This is basically just silencing a warning, right?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-Wno-unused-functionis supported by at least clang 3. Otherwise, it’d need to be added conditionally based on the clang version (e.g., #253740). Applying this patch without #241692 shouldn’t negatively affect anything.GHC 9.4.x does specify an LLVM version, but isn’t that for the LLVM backend? When I look at the result of the
preConfigurescript, it’s settingCC, etc to clang 16.However, when I drop this patch from my clang 16 branch (to get the specific error and check the build process), it builds successfully. The log shows numerous “errors” related to strict prototypes and this unused function, but they’re being treated as warnings. 🤨
I have no idea what changed or why it started working.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see, so you're saying that there is a difference between the clang version used for compiling GHC, and the version passed as the LLVM backend?
I'm not very familiar with area, so maybe I should let someone else do the review here.
Ah, I see. I wonder what changed for you?
So I guess this PR might end up not being needed?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That appears to be the case.
The only thing that’s changed system-wise is I’m now running the macOS 14 beta, but I don’t know why that would matter.
Possibly not. I can close it for now and reopen if it causes issues on Hydra. It’s very peculiar. In July, I had all the errors causing problems. When I circled back to test again in August, only GHC 9.4.x was failing (and even it’s building now). That was prior to my installing the macOS 14 beta. I was still on 13.5 at that time.