This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/69284] [5.3] SIGSEGV when running 32-bit result on MinGW when linked dynamically
- From: "daniel.f.starke at freenet dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Jan 2016 21:29:04 +0000
- Subject: [Bug target/69284] [5.3] SIGSEGV when running 32-bit result on MinGW when linked dynamically
- Auto-submitted: auto-generated
- References: <bug-69284-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69284
--- Comment #1 from Daniel Starke <daniel.f.starke at freenet dot de> ---
I have tried a couple of things to find the cause of this bug.
- using -O1 instead of -O3 when building GCC
- using -O2 instead of -O3 when building GCC
- using -fno-lto when building GCC
- using the defaults compile/link flags when building GCC
- removing the -mtune=core2 -march=core2 arguments from the compile/link flags
- configuring GCC with --enable-threads=win32 instead of --enable-threads=posix
Neither worked. And I noticed, that the resulting 32-bit libstdc++-6.dll was
way smaller than its 64-bit variant.
Then I changed from binutils 2.26.51 to 2.25.1 and I got a working
libstdc++-6.dll.
So I suspect that this is a binutils issue rather than a GCC issue.
I will report it to the binutils bug tracker later on.
This bug can be closed in my opinion.