-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Demangling: always build with NDEBUG #19258
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
Conversation
@swift-ci please test |
I don't like this. Can we use something other than |
@jrose-apple - we could use |
I would much rather keep the asserts and fix this problem some other way. |
@slavapestov - I really don't like the idea of providing an alternative implementation of |
f133a01
to
58f8f68
Compare
At least the build will be aborted with this version. @slavapestov - suggestions welcome :-) |
Okay, actually all of these unreachables come after |
We could use assert(false && ...) instead of llvm_unreachable in the demangler. |
@slavapestov - yeah, I suppose |
Using assert sounds good to me |
Build failed |
Avoid a dependency on LLVMSupport at runtime through the `llvm_unreachable`. This would pull in `llvm_unreachable_internal` in debug builds, which requires a runtime dependency on LLVMSupport which increases the size of the binary considerably.
58f8f68
to
9105eb3
Compare
@swift-ci please test and merge |
1 similar comment
@swift-ci please test and merge |
@swift-ci please test macOS platform |
Avoid a dependency on LLVMSupport at runtime through the
llvm_unreachable
.This would pull in
llvm_unreachable_internal
in debug builds, which requires aruntime dependency on LLVMSupport which increases the size of the binary
considerably. Always build with NDEBUG. Note that this effectively always
builds the Demangling library WITHOUT asserts :-(.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.