4 ms·

btw, the current dev version of clang is broken for months. It crashes on a failed assertion when I'm trying to compile erlang or mplayer+ffmpeg. It also failed

btw, the current dev version of clang is broken for months. It crashes on a failed assertion when I'm trying to compile erlang or mplayer+ffmpeg. It also failed to build racket - the resulting binary eats all the memory and dies.) Gcc does the job. So, it seems that while running after C++ features they ruined the plain old C.)

stephencanon 14y ago
It works great on my C sources; have you reported the failure(s)?
- dschiptsov 14y ago
  clang -m64 -march=native -mtune=native -O3 -I/home/schiptsov/Compile/otp/erts/x86_64-unknown-linux-gnu -D_GNU_SOURCE -DERTS_SMP -DHAVE_CONFIG_H -Wall -Wstrict-prototypes -Wmissing-prototypes -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -Ix86_64-unknown-linux-gnu/opt/smp -Ibeam -Isys/unix -Isys/common -Ix86_64-unknown-linux-gnu -Izlib -Ipcre -Ihipe -I../include -I../include/x86_64-unknown-linux-gnu -I../include/internal -I../include/internal/x86_64-unknown-linux-gnu -c beam/beam_emu.c -o obj/x86_64-unknown-linux-gnu/opt/smp/beam_emu.o clang: /home/schiptsov/Compile/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp:2050: bool <anonymous namespace>::LoopVectorizationLegality::canVectorize(): Assertion `TheLoop->getLoopPreheader() && "No preheader!!"' failed.
- dschiptsov 14y ago
  CC libavcodec/flashsvenc.o clang: /home/schiptsov/Compile/llvm/lib/Analysis/LazyValueInfo.cpp:613: bool <anonymous namespace>::LazyValueInfoCache::solveBlockValueNonLocal(<anonymous>::LVILatticeVal &, llvm::Value *, llvm::BasicBlock *): Assertion `isa<Argument>(Val) && "Unknown live-in to the entry block"' failed.
jevinskie 14y ago
LLVM and Clang have nightly buildbots that check for regressions. They are quite fastidiously maintained. The project would really appreciate your help and you can do so by submitting a bug report with steps to reproduce and build artifacts. The bugfix will contain a test case, likely a minimal reduction of your repro, that will be run in the buildbots to make sure that you never see the same problem again. And I do not believe that they have sacrificed anything to support both C and C++ (including partial support for their '11 variants). The codebase is abstracted away from the C/C++ differences where it makes sense. It is an impressively comprehensible compiler! http://llvm.org/bugs/ http://llvm.org/bugs/

stephencanon 14y ago

It works great on my C sources; have you reported the failure(s)?

dschiptsov 14y ago
clang -m64 -march=native -mtune=native -O3 -I/home/schiptsov/Compile/otp/erts/x86_64-unknown-linux-gnu -D_GNU_SOURCE -DERTS_SMP -DHAVE_CONFIG_H -Wall -Wstrict-prototypes -Wmissing-prototypes -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -DPOSIX_THREADS -D_POSIX_THREAD_SAFE_FUNCTIONS -Ix86_64-unknown-linux-gnu/opt/smp -Ibeam -Isys/unix -Isys/common -Ix86_64-unknown-linux-gnu -Izlib -Ipcre -Ihipe -I../include -I../include/x86_64-unknown-linux-gnu -I../include/internal -I../include/internal/x86_64-unknown-linux-gnu -c beam/beam_emu.c -o obj/x86_64-unknown-linux-gnu/opt/smp/beam_emu.o clang: /home/schiptsov/Compile/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp:2050: bool <anonymous namespace>::LoopVectorizationLegality::canVectorize(): Assertion `TheLoop->getLoopPreheader() && "No preheader!!"' failed.
dschiptsov 14y ago
CC libavcodec/flashsvenc.o clang: /home/schiptsov/Compile/llvm/lib/Analysis/LazyValueInfo.cpp:613: bool <anonymous namespace>::LazyValueInfoCache::solveBlockValueNonLocal(<anonymous>::LVILatticeVal &, llvm::Value *, llvm::BasicBlock *): Assertion `isa<Argument>(Val) && "Unknown live-in to the entry block"' failed.

jevinskie 14y ago

LLVM and Clang have nightly buildbots that check for regressions. They are quite fastidiously maintained. The project would really appreciate your help and you can do so by submitting a bug report with steps to reproduce and build artifacts. The bugfix will contain a test case, likely a minimal reduction of your repro, that will be run in the buildbots to make sure that you never see the same problem again. And I do not believe that they have sacrificed anything to support both C and C++ (including partial support for their '11 variants). The codebase is abstracted away from the C/C++ differences where it makes sense. It is an impressively comprehensible compiler! http://llvm.org/bugs/ http://llvm.org/bugs/