summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/support/gmodules.py
diff options
context:
space:
mode:
authorBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2017-10-24 11:59:20 +0000
committerBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2017-10-24 11:59:20 +0000
commite1285e3cdf6bd34311611070ffe2ac6a6af76276 (patch)
treebd632e09641c2bfd24657e3d4efb01ccb84a86cc /lldb/packages/Python/lldbsuite/support/gmodules.py
parenta17480d6021b1be73ba17a0898bc486378f64945 (diff)
downloadbcm5719-llvm-e1285e3cdf6bd34311611070ffe2ac6a6af76276.tar.gz
bcm5719-llvm-e1285e3cdf6bd34311611070ffe2ac6a6af76276.zip
[LangRef] Update description of Constant Expressions
Summary: When describing trunc/zext/sext/ptrtoint/inttoptr in the chapter about Constant Expressions we now simply refer to the Instruction Reference. As far as I know there are no difference when it comes to the semantics and the argument constraints. The only difference is that the syntax is slighly different for the constant expressions, regarding the use of parenthesis in constant expressions. Referring to the Instruction Reference is the same solution as already used for several other operations, such as bitcast. The main goal was to add information that vector types are allowed also in trunc/zext/sext/ptrtoint/inttoptr constant expressions. That was not explicitly mentioned earlier, and resulted in some questions in the review of https://reviews.llvm.org/D38546 Reviewers: efriedma, majnemer Reviewed By: efriedma Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D39165 llvm-svn: 316429
Diffstat (limited to 'lldb/packages/Python/lldbsuite/support/gmodules.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud