[LLVMbugs] [Bug 24178] New: clang crashes with SIGSEGV during "LLVM IR generation of compound statement ('{}')"

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Sat Jul 18 08:39:26 PDT 2015


https://llvm.org/bugs/show_bug.cgi?id=24178

            Bug ID: 24178
           Summary: clang crashes with SIGSEGV during "LLVM IR generation
                    of compound statement ('{}')"
           Product: clang
           Version: 3.6
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: felix.morgner at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

When compiling the attached source on Arch Linux using the clang 3.6.2 release
found in the official repository running on 'armv7l-unknown-linux-gnueabihf' I
get the following stack dump:

0.    Program arguments: /usr/bin/clang -cc1 -triple
armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier
-main-file-name device.cpp -mrelocation-model static -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-fuse-init-array -target-cpu cortex-a8 -target-abi aapcs-linux -mfloat-abi hard
-target-linker-version 2.25.0 -dwarf-column-info -coverage-file
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/build/src/CMakeFiles/device.dir/device.cpp.o
-resource-dir /usr/bin/../lib/clang/3.6.2 -D ASIO_STANDALONE -D NDEBUG -I
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/include -internal-isystem
/usr/bin/../lib/gcc/armv7l-unknown-linux-gnueabihf/5.1.0/../../../../include/c++/5.1.0
-internal-isystem
/usr/bin/../lib/gcc/armv7l-unknown-linux-gnueabihf/5.1.0/../../../../include/c++/5.1.0/armv7l-unknown-linux-gnueabihf
-internal-isystem
/usr/bin/../lib/gcc/armv7l-unknown-linux-gnueabihf/5.1.0/../../../../include/c++/5.1.0/backward
-internal-isystem /usr/local/include -internal-isystem
/usr/bin/../lib/clang/3.6.2/include -internal-externc-isystem /include
-internal-externc-isystem /usr/include -O3 -Wall -Wextra -Werror -pedantic
-std=c++14 -fdeprecated-macro -fdebug-compilation-dir
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/build/src -ferror-limit
19 -fmessage-length 119 -mstackrealign -fno-signed-char -fobjc-runtime=gcc
-fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics
-vectorize-loops -vectorize-slp -o CMakeFiles/device.dir/device.cpp.o -x c++
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/src/device.cpp 
1.    <eof> parser at end of file
2.   
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/src/device.cpp:14:11:
LLVM IR generation of declaration 'tapper'
3.   
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/src/device.cpp:17:11:
Generating code for declaration 'tapper::device::device'
4.   
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/src/device.cpp:18:5: LLVM
IR generation of compound statement ('{}')
5.   
/home/gitlab-runner/builds/c5102916/0/fmorgner/tapper/src/device.cpp:24:7: LLVM
IR generation of compound statement ('{}')

The issue doesn't seem to occur on x86_64.

This is the 'script' used:

"/usr/bin/clang" "-cc1" "-triple" "armv7-unknown-linux-gnueabihf" "-emit-obj"
"-disable-free" "-disable-llvm-verifier" "-main-file-name" "device.cpp"
"-mrelocation-model" "static" "-mthread-model" "posix" "-mdisable-fp-elim"
"-fmath-errno" "-masm-verbose" "-mconstructor-aliases" "-fuse-init-array"
"-target-cpu" "cortex-a8" "-target-abi" "aapcs-linux" "-mfloat-abi" "hard"
"-target-linker-version" "2.25.0" "-dwarf-column-info" "-D" "ASIO_STANDALONE"
"-D" "NDEBUG" "-O3" "-Wall" "-Wextra" "-Werror" "-pedantic" "-std=c++14"
"-fdeprecated-macro" "-ferror-limit" "19" "-fmessage-length" "119"
"-mstackrealign" "-fno-signed-char" "-fobjc-runtime=gcc" "-fcxx-exceptions"
"-fexceptions" "-fdiagnostics-show-option" "-fcolor-diagnostics"
"-vectorize-loops" "-vectorize-slp" "-x" "c++" "device-200786.cpp"

-- 
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/20150718/77cf6ae4/attachment.html>


More information about the llvm-bugs mailing list