summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/c
diff options
context:
space:
mode:
authorMatt Arsenault <Matthew.Arsenault@amd.com>2017-11-07 00:06:32 +0000
committerMatt Arsenault <Matthew.Arsenault@amd.com>2017-11-07 00:06:32 +0000
commit6119f80034deca6c53fdeca746e3cb654ebad0c5 (patch)
tree6e7feeca8b8317ad609ec22e64793d17b3d6c1c2 /lldb/packages/Python/lldbsuite/test/lang/c
parent7957b08e87ce314ca644e079a481ac3819f943bc (diff)
downloadbcm5719-llvm-6119f80034deca6c53fdeca746e3cb654ebad0c5.tar.gz
bcm5719-llvm-6119f80034deca6c53fdeca746e3cb654ebad0c5.zip
AMDGPU: Remove redundant combine
This combine was already done in two places. The generic combiner already has done this since r217610, for adds (with a single use). This one was added in r303641, and added support for handling or as well. r313251 later added support to the generic combine for or. It also turns out the isOrEquivalentToAdd check is not necessary for this combine. Additionally, we already reproduce this combine in yet another place in the backend, although in that version multiple uses of the add are still folded if it will allow a fold into the addressing mode. That version needs to be improved to understand ors though, as well as the correct legal offsets for private. llvm-svn: 317526
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud