DavidSpickett added a comment. > I like it the above approach with more enums for the high and low code/data. > Not sure if eTypeAny makes sense in the GetAddressMask(eTypeAny) scenario
It could be like the `FixAny` method, a fallback when you don't know either way. `eTypeAny` returns `FixAnyAddress(~0)` essentially. Or it could or together all the masks but while that's good for curiosity's sake (what address bits are "safe"?) you would still need specific masks to construct an address for specific purposes. It could fail, but then we're carrying around a Status object for one case, and that seems a shame. Unless we can think of other failure modes we haven't considered yet. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D155905/new/ https://reviews.llvm.org/D155905 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
