Not always do we want to greedily merge the bits
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
1,300 ms | x64 debian > libomp.lock::omp_init_lock.c |
Event Timeline
Comment Actions
TBH I think you'd be better off splitting ScaleBitMask into 2 methods rather than using an enum - unless you have a strong use case for needing to select between the 2 at runtime
Comment Actions
TBH I think you'd be better off splitting ScaleBitMask into 2 methods rather than using an enum - unless you have a strong use case for needing to select between the 2 at runtime
clang-tidy: warning: invalid case style for function 'ScaleBitMask' [readability-identifier-naming]
not useful