-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clang++ crashes when compiling simple programs #1195
Comments
Hi guys, Maybe the crash log would be usefull:
Thanks. Yanan |
Probably the same bug in the llvm/clang bugtracker: https://llvm.org/bugs/show_bug.cgi?id=26900#c1 |
Just tested with updated packages. No issue with -O0, -O1, -O2, -O3. |
Hi Mati865, Which clang do you use? mingw-w64-i686-clang or mingw-w64-i686-clang-svn. I tried again but still failed. Thanks. Yanan |
I also have full set of GCC tools. |
Hi Mati865, My PC runs Windows 7 x86. I redid as below:
But I still could see the crash. Thanks. Yanan |
Ok got crash using this steps. Probably clang and it's libs need to be rebuild. EDIT: Could be related https://llvm.org/bugs/show_bug.cgi?id=11549 |
Rebuilding clang not help |
In Cygwin i686-w64-mingw32-clang++ 3.7.1 doesn't crash. Maybe someone experienced with Cygwin could check what they changed? |
Is there a status update to this bug? I've tried to compile zlib-ng; Intel's threading building blocks and lua 5.1 today with the most recent package of mingw-w64-i686-clang (3.8.0-3) but without success. The 64-bit-Clang version compiles fine, though (with appropriately modified Makefiles), as does GCC. But I need explicitly the 32-bit-DLL's for performance comparison and compatibility reasons. Are there any chances to get this fixed soon? |
Hi guys,
I tried to use clang++ to build a program but failed. And then I tested clang++ with a simple program.
The command that I run is:
My test program is very simple:
And this is the clang version:
I am not sure if it is a LLVM or Clang bug but I would like to report bug here first.
Thanks.
Yanan
The text was updated successfully, but these errors were encountered: