diff options
author | Diana Picus <diana.picus@linaro.org> | 2018-01-04 10:54:57 +0000 |
---|---|---|
committer | Diana Picus <diana.picus@linaro.org> | 2018-01-04 10:54:57 +0000 |
commit | 37ae9f68a404f2684e83d4ad10c051ad7e89b1c8 (patch) | |
tree | 93b972760187fe87a6f97632a36bf47877227278 /lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands | |
parent | 4d5e34b221d140dfd8829a0050a8a8d84e7a5983 (diff) | |
download | bcm5719-llvm-37ae9f68a404f2684e83d4ad10c051ad7e89b1c8.tar.gz bcm5719-llvm-37ae9f68a404f2684e83d4ad10c051ad7e89b1c8.zip |
[ARM GlobalISel] Fix selection of pointer constants
We used to handle G_CONSTANT with pointer type by forcing the type of
the result register to s32 and then letting TableGen handle it.
Unfortunately, setting the type only works for generic virtual
registers, that haven't yet been constrained to a register class (e.g.
those used only by a COPY later on). If the result register has already
been constrained as a use of a previously selected instruction, then
setting the type will assert.
It would be nice to be able to teach TableGen to select pointer
constants the same as integer constants, but since it's such an edge
case (at the moment the only pointer constant that we're generally
interested in is 0, and that is mostly used for comparisons and selects,
which are also not supported by TableGen) it's probably not worth the
effort right now. Instead, handle pointer constants with some trivial
handwritten code.
llvm-svn: 321793
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands')
0 files changed, 0 insertions, 0 deletions