diff options
| author | Juergen Ributzka <juergen@apple.com> | 2014-04-26 02:58:04 +0000 |
|---|---|---|
| committer | Juergen Ributzka <juergen@apple.com> | 2014-04-26 02:58:04 +0000 |
| commit | a6bda8bae25be0b1cc0fa64fa7035a47e3a3b6a2 (patch) | |
| tree | ce323e8a5f39436923a1f0140d324d4a894dff1b /llvm/lib/Analysis/LazyCallGraph.cpp | |
| parent | c46e9b0423683ccb642573e3d36ef95fcc2c68ac (diff) | |
| download | llvm-a6bda8bae25be0b1cc0fa64fa7035a47e3a3b6a2.zip llvm-a6bda8bae25be0b1cc0fa64fa7035a47e3a3b6a2.tar.gz llvm-a6bda8bae25be0b1cc0fa64fa7035a47e3a3b6a2.tar.bz2 | |
[DAG] During DAG legalization keep opaque constants even after expanding.
The included test case would return the incorrect results, because the expansion
of an shift with a constant shift amount of 0 would generate undefined behavior.
This is because ExpandShiftByConstant assumes that all shifts by constants with
a value of 0 have already been optimized away. This doesn't happen for opaque
constants and usually this isn't a problem, because opaque constants won't take
this code path - they are not supposed to. In the case that the opaque constant
has to be expanded by the legalizer, the legalizer would drop the opaque flag.
In this case we hit the limitations of ExpandShiftByConstant and create incorrect
code.
This commit fixes the legalizer by not dropping the opaque flag when expanding
opaque constants and adding an assertion to ExpandShiftByConstant to catch this
not supported case in the future.
This fixes <rdar://problem/16718472>
llvm-svn: 207304
Diffstat (limited to 'llvm/lib/Analysis/LazyCallGraph.cpp')
0 files changed, 0 insertions, 0 deletions