Skip to content

build: disable warning -Wunreachable-code-break#15416

Closed
vszakats wants to merge 1 commit intocurl:masterfrom
vszakats:drop-warning
Closed

build: disable warning -Wunreachable-code-break#15416
vszakats wants to merge 1 commit intocurl:masterfrom
vszakats:drop-warning

Conversation

@vszakats
Copy link
Member

@vszakats vszakats commented Oct 25, 2024

This warning remains silent in unity builds. Since we're using unity
in CI for most jobs, warnings remain undetected there.
Disable them for all builds to avoid a surprise warning outside our CI.

The issue caught by the warning is useful for a tidy codebase, but
doesn't affect executed code. It was enabled in
84338c4 #12331 (2023-11-15).

llvm source: https://github.com/llvm/llvm-project/blob/fee2953f23bd8a8a71e574e6a8db08033778d3a4/clang/lib/Sema/AnalysisBasedWarnings.cpp#L125-L134
llvm issue: llvm/llvm-project#71046

Follow-up to 7c023c3 #15384

This warning remains silent in unity builds. Since we're using unity
build in CI for most jobs, warnings remain undetected there.
Disable them for all builds to avoid a surprise warning outside our CI.

The issue caught by the warning is useful for a tidy codebase, but
doesn't affect executed code. It was enabled in
84338c4 curl#12331 (2023-11-15).

llvm source: https://github.com/llvm/llvm-project/blob/fee2953f23bd8a8a71e574e6a8db08033778d3a4/clang/lib/Sema/AnalysisBasedWarnings.cpp#L125-L134
llvm issue: llvm/llvm-project#71046

Follow-up to 7c023c3 curl#15384
@vszakats vszakats added the build label Oct 25, 2024
@dfandrich
Copy link
Contributor

Analysis of PR #15416 at 2e771c41:

Test 271 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Generated by Testclutch

@vszakats vszakats closed this in 0da1489 Oct 27, 2024
@vszakats vszakats deleted the drop-warning branch October 27, 2024 13:11
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
This warning remains silent in unity builds. Since we're using unity
in CI for most jobs, warnings remain undetected there.
Disable them for all builds to avoid a surprise warning outside our CI.

The issue caught by the warning is useful for a tidy codebase, but
doesn't affect executed code. It was enabled in
84338c4 curl#12331 (2023-11-15).

llvm source: https://github.com/llvm/llvm-project/blob/fee2953f23bd8a8a71e574e6a8db08033778d3a4/clang/lib/Sema/AnalysisBasedWarnings.cpp#L125-L134
llvm issue: llvm/llvm-project#71046

Follow-up to 7c023c3 curl#15384
Closes curl#15416
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants