[llvm-bugs] [Bug 42881] New: LoopRotate causes a miscompilation
via llvm-bugs
llvm-bugs at lists.llvm.org
Sun Aug 4 06:02:04 PDT 2019
https://bugs.llvm.org/show_bug.cgi?id=42881
Bug ID: 42881
Summary: LoopRotate causes a miscompilation
Product: libraries
Version: 9.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Loop Optimizer
Assignee: unassignedbugs at nondot.org
Reporter: aykevanlaethem at gmail.com
CC: llvm-bugs at lists.llvm.org
I have the following IR:
---
target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64"
target triple = "arm-none-eabi"
@_sbss = external global i8*
@_ebss = external global i8*
define fastcc void @runtime.preinit() {
entry:
br label %for.loop
for.loop: ; preds = %for.body, %entry
%0 = phi i32 [ ptrtoint (i8** @_sbss to i32), %entry ], [ %3, %for.body ]
%1 = icmp eq i32 %0, ptrtoint (i8** @_ebss to i32)
br i1 %1, label %for.done, label %for.body
for.body: ; preds = %for.loop
%2 = inttoptr i32 %0 to i32*
store i32 0, i32* %2, align 4
%3 = add i32 %0, 4
br label %for.loop
for.done: ; preds = %for.loop
ret void
}
---
When I run the following command:
opt-9 -S -loop-rotate -o bug.opt.ll bug.ll
the runtime.preinit function is optimized to the following:
---
define fastcc void @runtime.preinit() {
entry:
br label %for.body
for.body: ; preds = %entry, %for.body
%0 = phi i32 [ ptrtoint (i8** @_sbss to i32), %entry ], [ %2, %for.body ]
%1 = inttoptr i32 %0 to i32*
store i32 0, i32* %1, align 4
%2 = add i32 %0, 4
%3 = icmp eq i32 %2, ptrtoint (i8** @_ebss to i32)
br i1 %3, label %for.done, label %for.body
for.done: ; preds = %for.body
ret void
}
---
In other words, it looks like LoopRotate thinks the comparison in the loop
header can be done after the first store.
I believe this optimization is incorrect, as there is no indication in the IR
that it is okay to store to @_sbss unconditionally. In fact, because @_sbss and
@_ebss happen to be aliases this causes a loop zeroing the entire address space
until it crashes.
Thinking a bit more about this, it seems like LoopRotate introduces an
off-by-one error in the loop: before this optimization the loop would zero all
memory before @_ebss while after the optimization it zeroes all memory
including the word behind @_ebss (which lies outside of the range it is
supposed to zero).
If this is a correct optimization, please let me know why so I can fix this in
the compiler frontend or the runtime library.
Note that this bug is present in both LLVM 9 and LLVM 8 (from apt.llvm.org), so
it affects the current stable version as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190804/cfd55c00/attachment-0001.html>
More information about the llvm-bugs
mailing list