aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/Support/CommandLineTest.cpp
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-05-07 15:58:20 +0000
committerPavel Labath <pavel@labath.sk>2019-05-07 15:58:20 +0000
commit0ff89dacaf476e4e18195a9bc6f1fdddb91e20ad (patch)
tree193aeafbf5150e950288578dc4c9f82e13182aff /llvm/unittests/Support/CommandLineTest.cpp
parentb33fdb7768e5de5fbeb23f65d8d455e7ca88b021 (diff)
downloadllvm-0ff89dacaf476e4e18195a9bc6f1fdddb91e20ad.zip
llvm-0ff89dacaf476e4e18195a9bc6f1fdddb91e20ad.tar.gz
llvm-0ff89dacaf476e4e18195a9bc6f1fdddb91e20ad.tar.bz2
PostfixExpression: Use signed integers in IntegerNode
Summary: This is necessary to support parsing expressions like ".cfa -16 + ^", as that format is used in breakpad STACK CFI expressions. Since the PDB expressions use the same parser, this change will affect them too, but I don't believe that should be a problem in practice. If PDBs do contain the negative values, it's very likely that they are intended to be parsed the same way, and if they don't, then it doesn't matter. In case that we do ever need to handle this differently, we can always make the parser behavior customizable, or just use a different parser. To make sure that the integer size is big enough for everyone, I switch from using a (unsigned) 32-bit integer to a 64-bit (signed) one. Reviewers: amccarth, clayborg, aleksandr.urakov Subscribers: markmentovai, lldb-commits Differential Revision: https://reviews.llvm.org/D61311 llvm-svn: 360166
Diffstat (limited to 'llvm/unittests/Support/CommandLineTest.cpp')
0 files changed, 0 insertions, 0 deletions