On 2015-4-15 10:48, Norbert Pfeiler wrote:
> PCH on Windows did crash for *.gch files greater than 150 MiB or something.
> I don’t think that got fixed recently
This is the bug report:
Bug 56926 – Crash (without ICE) while compiling Boost.Math
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926
PCH on Windows did crash for *.gch files greater than 150 MiB or something.
I don’t think that got fixed recently…
2015-04-15 4:04 GMT+02:00 lh_mouse :
> Did you use *exactly the same command line options* (esp. -D -fPIC etc) in
> both generating and invoking the precompiled header?
> According t
Did you use *exactly the same command line options* (esp. -D -fPIC etc) in both
generating and invoking the precompiled header?
According to my experience, mismatched -fPIC -DPIC is known to crash g++ 4.4 on
Linux. I am not sure about other versions.
I have been using .gch files for mingw-w64-gc
So I noticed that including the following PCH header files file crashes g++
The content of which is given below.
#pragma once
#include
#include
#include
#ifdef __cplusplus
#include
#include
#include
#include
#include
#include
#define BOOST_ALL_DYN_LINK
#define BOOST_ALL_NO_LIB
Here is the compiler invocation
g++.exe -std=c++11 -Winvalid-pch -fpermissive -include "ktafx.h" -D_DEBUG
-D_USRDLL -DKT_THREAD_NAME=GAME -DBOOST_EXCEPTION_DISABLE
-DAFP_BINDATA_USE_OFFSET -DAVS_NDEBUG -DAVS_TARGET_WIN7 -DAVS_POINTER_64BIT
-D_WINDLL -D_UNICODE -DUNICODE -DKT_WRAPPER_EXPORTS -DMING
2015-04-14 19:13 GMT+02:00 James Franco :
> I am attempting to port a project from Visual Studio to Mingw 64 bit GCC.
> During the port when I attempt to build a certain component using Mingw g++
> through CodeBlocks I get the error
> "cc1plus.exe has stopped working." Is there a way for me to fig
I am attempting to port a project from Visual Studio to Mingw 64 bit GCC.
During the port when I attempt to build a certain component using Mingw g++
through CodeBlocks I get the error
"cc1plus.exe has stopped working." Is there a way for me to figure out what
might be the cause of this crash ? Cou
On 14.04.2015 10:32, Kai Tietz wrote:
> 2015-04-14 4:26 GMT+02:00 LRN:
>> subj
>>
> Patch is ok for master. About the exception-handler ... shouldn't we
> add handling to our CRT's exception-handler-routine instead? (at least
> for none MSC case).
I see a few exception handlers in CRT.
One is _gn
Hi LRN,
Patch is ok for master. About the exception-handler ... shouldn't we
add handling to our CRT's exception-handler-routine instead? (at least
for none MSC case).
Thanks,
Kai
2015-04-14 4:26 GMT+02:00 LRN :
> subj
>
> --
> O< ascii ribbon - stop html email! - www.asciiribbon.org
>
> --
