GH-131296: fix clang-cl warning in tracemalloc.c#131374
Closed
Uh oh!
There was an error while loading. Please reload this page.
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.
This one is really interesting. Only clang-cl issues it - not clang or GCC on Linux: https://godbolt.org/z/57oaaTcbT
Interestingly enough, clang-cl even emits this warning without any options given (i.e. the default warning level), on the not taken branch in
Py_MIN(x, y) (((x) > (y)) ? (y) : (x)).I had to use C++ on godbolt, because clang-cl is not available as C compiler, but I get the same error for that file when compiling the C file
tracemalloc.clocally.The fix is easy, although seeming very unneeded :(