summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py
diff options
context:
space:
mode:
authorSimon Atanasyan <simon@atanasyan.com>2019-10-11 12:33:12 +0000
committerSimon Atanasyan <simon@atanasyan.com>2019-10-11 12:33:12 +0000
commitb051a19aa02dddb554d913941868a9dd0837d554 (patch)
treecaa9533cfd5a8c0936cbbb00da08a17ba7ad3b7a /lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py
parentb95713784a3c4105ade2ded5309b30f51497e810 (diff)
downloadbcm5719-llvm-b051a19aa02dddb554d913941868a9dd0837d554.tar.gz
bcm5719-llvm-b051a19aa02dddb554d913941868a9dd0837d554.zip
[mips] Fix loading "double" immediate into a GPR and FPR
If a "double" (64-bit) value has zero low 32-bits, it's possible to load such value into a GP/FP registers as an instruction immediate. But now assembler loads only high 32-bits of the value. For example, if a target register is GPR the `li.d $4, 1.0` instruction converts into the `lui $4, 16368` one. As a result, we get `0x3FF00000` in the register. While a correct representation of the `1.0` value is `0x3FF0000000000000`. The patch fixes that. Differential Revision: https://reviews.llvm.org/D68776 llvm-svn: 374544
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/sbstructureddata/TestStructuredDataAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud