-
Notifications
You must be signed in to change notification settings - Fork 39.2k
ci, iwyu: Treat warnings as errors for specific directories #31308
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
Changes from all commits
56f2a68
bdb8ead
57a3eac
02d2b5a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,16 @@ | ||
| # Nothing for now. | ||
| [ | ||
| # Compiler intrinsics. | ||
| # See: https://github.com/include-what-you-use/include-what-you-use/issues/1764. | ||
| { "include": [ "<emmintrin.h>", "private", "<immintrin.h>", "public" ] }, | ||
| { "include": [ "<smmintrin.h>", "private", "<immintrin.h>", "public" ] }, | ||
| { "include": [ "<tmmintrin.h>", "private", "<immintrin.h>", "public" ] }, | ||
|
Comment on lines
+2
to
+6
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This has been addressed upstream in include-what-you-use/include-what-you-use@6a113bc. |
||
|
|
||
| # libc symbols. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Has this been upstreamed / why is it needed?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Not yet.
Otherwise, IWYU will suggest platform-specific headers instead of the standard one provided by the C library.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. seems fine to upstream this, but this shouldn't be a blocker, i'd say
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Is there anything blocking that? It'd be good if we'd atleast report issues upstream, before adding workarounds (with little-to-no documentation).
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An upstream issue: include-what-you-use/include-what-you-use#1809. |
||
| { "symbol": ["AT_HWCAP", "private", "<sys/auxv.h>", "public"] }, | ||
| { "symbol": ["AT_HWCAP2", "private", "<sys/auxv.h>", "public"] }, | ||
|
|
||
| # Fixed in https://github.com/include-what-you-use/include-what-you-use/pull/1706. | ||
| { "symbol": ["SEEK_CUR", "private", "<cstdio>", "public"] }, | ||
| { "symbol": ["SEEK_END", "private", "<cstdio>", "public"] }, | ||
| { "symbol": ["SEEK_SET", "private", "<cstdio>", "public"] }, | ||
| ] | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,6 +9,7 @@ | |
|
|
||
| #include <cstddef> | ||
| #include <cstdint> | ||
| #include <span> | ||
| #include <string> | ||
|
|
||
| /** | ||
|
|
||
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.
could we fix this in https://github.com/bitcoin-core/leveldb-subtree/pulls instead?
I have opened bitcoin-core/leveldb-subtree#56 (I'm also fine with doing it in a different PR, just wanted to give the possibility to solve it in a cleaner way)
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.
No objection, but I am not sure we should diverge the subtree for a test-only patch. Also, the patch is pre-existing, so it seems a bit unrelated to this pull.
Ideally, Google would fix the UB in some way or another, and then we can pull whatever their fix was, but that shouldn't be a blocker here.
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.
The main leveledb repo doesn't even compile for the past 8 months, not sure why we would wait for them. But as I mentioned, I don't mind doing it after the PR, just seems cleaner if we didn't need to change this section again.