[llvm-bugs] [Bug 33231] New: poor handling of io errors?

via llvm-bugs llvm-bugs at lists.llvm.org
Tue May 30 14:10:34 PDT 2017


            Bug ID: 33231
           Summary: poor handling of io errors?
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: matthias.krueger at famsik.de
                CC: llvm-bugs at lists.llvm.org

lld @ 3710f10def28ec96b20b86dea048f9f11260734e / 
git-svn-id: https://llvm.org/svn/llvm-project/lld/trunk@304206

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" \
        -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" \

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?

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/20170530/f30dc68d/attachment-0001.html>

More information about the llvm-bugs mailing list