<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - opt -run-twice raises segmentation fault"
href="https://bugs.llvm.org/show_bug.cgi?id=44382">44382</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>opt -run-twice raises segmentation fault
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Transformation Utilities
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>juneyoung.lee@sf.snu.ac.kr
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>```
$ 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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>