[PATCH] D75695: [StackProtector] Catch direct out-of-bounds when checking address-takenness

Eli Friedman via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Mar 12 13:01:32 PDT 2020

Previous message: [PATCH] D75695: [StackProtector] Catch direct out-of-bounds when checking address-takenness
Next message: [PATCH] D75695: [StackProtector] Catch direct out-of-bounds when checking address-takenness
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

efriedma added a comment.

I think it would be more straightforward to reason about the behavior here if you just pass down the number of bytes that are known safe to dereference, instead of "AllocType".


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D75695/new/

https://reviews.llvm.org/D75695

Previous message: [PATCH] D75695: [StackProtector] Catch direct out-of-bounds when checking address-takenness
Next message: [PATCH] D75695: [StackProtector] Catch direct out-of-bounds when checking address-takenness
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the llvm-commits mailing list