public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56926] Crash (without ICE) while compiling Boost.Math
Date: Fri, 22 May 2015 02:38:00 -0000	[thread overview]
Message-ID: <bug-56926-4-3pbIsGMsVp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56926-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926

--- Comment #12 from asmwarrior <asmwarrior at gmail dot com> ---
Hi, I just did a test on the cygwin 32bit tool chain.
1, download the cygwin installer.
2, install  gcc-g++ 4.9.2 and boost 1.57 package
3, run the steps in comment 6, except that you don't need to add the
"-ID:\mingw-builds\boost_1_55_0" in the build command, because we can use the
boost library installed from the previous step. 
4, when building the pch files, I get a 318M pch.h.gch file
5, when building the object file, I get a 365K test.o file

So, this bug doesn't happen in the cygwin tool chain, and it looks like the bug
only happens in the MinGW and MinGW-W64 tool chain.

Any ideas what is the reason of this bug? Maybe, someone can supply a debug
version of g++, and let help to run under GDB.


  parent reply	other threads:[~2015-05-22  2:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 19:13 [Bug c++/56926] New: " vanboxem.ruben at gmail dot com
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 [this message]
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-3pbIsGMsVp@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: link
Be 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).