kubamracek wrote: > would prefer to make more multiple, more conservative steps
I bet @nikic would agree with this ^ too. To me it sounds that we can untangle the individual parts/steps: classification in frontend, use-based (behavior change) on sspstrong, padding fix on basic (behavior change), big/small classification (behavior change). Even if some of the steps get blocked on a security sign-off, it sounds like a good idea to proceed so that we're in a better position to actually make the changes when we're ready? The preliminary step of moving basic classification to Clang (mostly done in this PR) seems not blocked on anything. If we all agree on the final state, any objections towards pursing individual steps? https://github.com/llvm/llvm-project/pull/183623 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
