https://bugs.llvm.org/show_bug.cgi?id=44382
Bug ID: 44382
Summary: opt -run-twice raises segmentation fault
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Transformation Utilities
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
```
$ cat aa.ll
define void @f() {
ret void
}
$ opt aa.ll -run-twice
WARNING: You're attempting to print out a bitcode file.
This is inadvisable as it may cause display problems. If
you REALLY want to taste LLVM bitcode first-hand, you
can force output with the `-f' option.
Stack dump:
0. Program arguments: /Users/juneyounglee//llvm/build/bin/opt ./aa.ll
-run-twice
0 opt 0x000000010e892835
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1 opt 0x000000010e891488 llvm::sys::RunSignalHandlers() +
248
2 opt 0x000000010e892e7c SignalHandler(int) + 268
3 libsystem_platform.dylib 0x00007fff708b342d _sigtramp + 29
4 opt 0x000000010e0cea09 forEachUser(llvm::Value const*,
llvm::SmallPtrSet<llvm::Value const*, 32u>&, llvm::function_ref<bool
(llvm::Value const*)>) + 41
5 libdyld.dylib 0x00007fff706ba7fd start + 1
6 libdyld.dylib 0x0000000000000003 start + 18446603338630060039
Segmentation fault: 11
```
This seems to be relevant with whether the input module has ever been updated
by passes.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
