diff options
author | Hal Finkel <hfinkel@anl.gov> | 2014-12-14 05:53:19 +0000 |
---|---|---|
committer | Hal Finkel <hfinkel@anl.gov> | 2014-12-14 05:53:19 +0000 |
commit | 4104a1a3460c06ac436a7d27763984d0884aef40 (patch) | |
tree | afe92edbe8b399350f07e19f7d99ef26927bf893 /clang/lib/AST/ExprConstant.cpp | |
parent | 0215c88f0036553a954ce102f0f8aebf7a5f0a45 (diff) | |
download | bcm5719-llvm-4104a1a3460c06ac436a7d27763984d0884aef40.tar.gz bcm5719-llvm-4104a1a3460c06ac436a7d27763984d0884aef40.zip |
[PowerPC] Handle cmp op promotion for SELECT[_CC] nodes in PPCTL::DAGCombineExtBoolTrunc
PPCTargetLowering::DAGCombineExtBoolTrunc contains logic to remove unwanted
truncations and extensions when dealing with nodes of the form:
zext(binary-ops(binary-ops(trunc(x), trunc(y)), ...)
There was a FIXME in the implementation (now removed) regarding the fact that
the function would abort the transformations if any of the non-output operands
of a SELECT or SELECT_CC node would need to be promoted (because they were
also output operands, for example). As a result, we continued to generate
unnecessary zero-extends for code such as this:
unsigned foo(unsigned a, unsigned b) {
return (a <= b) ? a : b;
}
which would produce:
cmplw 0, 3, 4
isel 3, 4, 3, 1
rldicl 3, 3, 0, 32
blr
and now we produce:
cmplw 0, 3, 4
isel 3, 4, 3, 1
blr
which is better in the obvious way.
llvm-svn: 224213
Diffstat (limited to 'clang/lib/AST/ExprConstant.cpp')
0 files changed, 0 insertions, 0 deletions