summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct
diff options
context:
space:
mode:
authorMichael Kuperstein <mkuper@google.com>2016-09-01 17:59:24 +0000
committerMichael Kuperstein <mkuper@google.com>2016-09-01 17:59:24 +0000
commit65bc3c89ffcf7290d7a676c3100edbb3a4b584a1 (patch)
tree9e7152026f65189462eb70d15a46db501dbfe50a /lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct
parentb28fe0307f2cf7620a92cb594d04e0e6b342a78d (diff)
downloadbcm5719-llvm-65bc3c89ffcf7290d7a676c3100edbb3a4b584a1.tar.gz
bcm5719-llvm-65bc3c89ffcf7290d7a676c3100edbb3a4b584a1.zip
[DAGCombine] Don't fold a trunc if it feeds an anyext
Legalization tends to create anyext(trunc) patterns. This should always be combined - into either a single trunc, a single ext, or nothing if the types match exactly. But if we happen to combine the trunc first, we may pull the trunc away from the anyext or make it implicit (e.g. the truncate(extract) -> extract(bitcast) fold). To prevent this, we can avoid doing the fold, similarly to how we already handle fpround(fpextend). Differential Revision: https://reviews.llvm.org/D23893 llvm-svn: 280386
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud