summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-c-test/object.c
diff options
context:
space:
mode:
authorSam Parker <sam.parker@arm.com>2017-09-04 08:12:16 +0000
committerSam Parker <sam.parker@arm.com>2017-09-04 08:12:16 +0000
commit7cd826a321d96af6581e0b1a5d6ec9ad26dcc6c1 (patch)
treef23d88c5d107378b4c4b0127a9ea4011be21093a /llvm/tools/llvm-c-test/object.c
parent69e22789e1e8e65ec14b31586be76ce698933521 (diff)
downloadbcm5719-llvm-7cd826a321d96af6581e0b1a5d6ec9ad26dcc6c1.tar.gz
bcm5719-llvm-7cd826a321d96af6581e0b1a5d6ec9ad26dcc6c1.zip
[LoopUnroll][DebugInfo] Don't add metadata to unrolled remainder loop
Debug information can be, and was, corrupted when the runtime remainder loop was fully unrolled. This is because a !null node can be created instead of a unique one describing the loop. In this case, the original node gets incorrectly updated with the NewLoopID metadata. In the case when the remainder loop is going to be quickly fully unrolled, there isn't the need to add loop metadata for it anyway. Differential Revision: https://reviews.llvm.org/D37338 llvm-svn: 312471
Diffstat (limited to 'llvm/tools/llvm-c-test/object.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud