<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 - poor handling of io errors?"
href="https://bugs.llvm.org/show_bug.cgi?id=33231">33231</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>poor handling of io errors?
</td>
</tr>
<tr>
<th>Product</th>
<td>lld
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</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>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>matthias.krueger@famsik.de
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>lld @ 3710f10def28ec96b20b86dea048f9f11260734e /
git-svn-id: <a href="https://llvm.org/svn/llvm-project/lld/trunk@304206">https://llvm.org/svn/llvm-project/lld/trunk@304206</a>
91177308-0d34-0410-b5e6-96231b3b80d8
I was doing a 2 stage (first stage optimized for performance, seconds stage:)
cmake ../llvm -G "Ninja" \
-DCMAKE_BUILD_TYPE="Debug" \
-DLLVM_BINUTILS_INCDIR=/usr/include \
-DCMAKE_C_FLAGS="-march=native -Og -g3" \
-DCMAKE_CXX_FLAGS="-march=native -Og -g3" \
-DLLVM_OPTIMIZED_TABLEGEN=1 \
-DCMAKE_AR="${rootDir}/stage_1/build/bin/llvm-ar" \
-DCMAKE_RANLIB="${rootDir}/stage_1/build/bin/llvm-ranlib" \
-DLLVM_USE_LINKER="${rootDir}/stage_1/build/bin/ld.lld" \
-DLLVM_USE_SANITIZER="Address;Undefined" \
-DLLVM_PARALLEL_LINK_JOBS=1 \
-DLLVM_ENABLE_EXPENSIVE_CHECKS=1 \
build.
Everything went well until it came to linking the clang-5.0 binary.
After approximately one hour and 30 minutes, lld was still hogging disk IO
seemingly, (most of the time, there were around 10-20 megabyte/s read and a
fews kilobyte/s write here and there) and I killed the process.
There was close to no cpu consumption by lld and the clang binary was staying
at around 1.2 gigabyte of size.
It looked like lld hung. Unfortunately I killed it and didn't think about
attaching gdb. :(
Later I discovered that SMART disk monitoring threw some errors:
May 30 22:25:56 t420 smartd[1277]: Device: /dev/sda [SAT], 32 Currently
unreadable (pending) sectors
May 30 22:25:56 t420 smartd[1277]: Device: /dev/sda [SAT], 32 Offline
uncorrectable sectors
I wonder if lld hung because of these disk errors.
Does lld handle such errors gracefully?</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>