public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vanboxem.ruben at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56926] New: Crash (without ICE) while compiling Boost.Math Date: Thu, 11 Apr 2013 19:13:00 -0000 [thread overview] Message-ID: <bug-56926-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926 Bug #: 56926 Summary: Crash (without ICE) while compiling Boost.Math Classification: Unclassified Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: vanboxem.ruben@gmail.com When compiling the file libs\math\build\..\src\tr1\assoc_laguerre.cpp from Boost 1.52.0 or 1.53.0 (perhaps any other version is affected too), GCC causes a dirty crash providing me no way of getting a sensible backtrace or providing a preprocessed source for reproduction. The compile command is: "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -mthreads -fvisibility=hidden -Winvalid-pch -DBOOST_ALL_NO_LIB=1 -DBOOST_BUILD_PCH_ENABLED -I"bin.v2\libs\math\build\gcc-mingw-4.8.1\debug\link-static\threading-multi\..\src\tr1" -I"." -I"libs\math\src\tr1" -c -o "bin.v2\libs\math\build\gcc-mingw-4.8.1\debug\link-static\threading-multi\assoc_laguerre.o" "libs\math\build\..\src\tr1\assoc_laguerre.cpp" This does not happen with GCC 4.7. If there is anything I can try to give more output, please let me know. The crash happens before -save-temps outputs anything. The binaries are for Windows 64-bit and available here (but require Win64, I haven't tested the Linux binaries built with the exact same build process): http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/gcc-4.8-release/x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb.7z/download
next reply other threads:[~2013-04-11 19:13 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-11 19:13 vanboxem.ruben at gmail dot com [this message] 2013-04-12 8:42 ` [Bug c++/56926] " rguenth at gcc dot gnu.org 2013-10-15 0:57 ` asmwarrior at gmail dot com 2013-12-27 22:10 ` 1000hz.radiowave at gmail dot com 2013-12-28 9:22 ` asmwarrior at gmail dot com 2013-12-28 13:42 ` 1000hz.radiowave at gmail dot com 2014-02-26 1:14 ` ai.emma.me at gmail dot com 2014-10-15 22:48 ` andre at netzeband dot eu 2014-11-08 22:00 ` andre at netzeband dot eu 2015-05-20 13:42 ` asmwarrior at gmail dot com 2015-05-22 2:38 ` asmwarrior at gmail dot com 2015-05-22 7:31 ` asmwarrior at gmail dot com 2015-05-31 6:35 ` asmwarrior at gmail dot com 2015-05-31 7:59 ` asmwarrior at gmail dot com 2015-06-02 5:11 ` asmwarrior at gmail dot com 2015-06-02 8:08 ` ismail at donmez dot ws
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-56926-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).