https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
Christoph Reiter changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #10 from Eric Botcazou ---
> I'm wondering if there are any downsides to just removing "-static-libgcc"
> from both "--with-stage1-ldflags" and "--with-boot-ldflags".
None presumably, since you already have dependencies on DLLs.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #9 from Christoph Reiter ---
(In reply to Eric Botcazou from comment #8)
> > We currently link:
> >
> > shared: gmp, winpthread, zlib, zstd
> > static: mpc, mpfr, isl
> >
> > Not for any particular gcc related reason I think, some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #8 from Eric Botcazou ---
> We currently link:
>
> shared: gmp, winpthread, zlib, zstd
> static: mpc, mpfr, isl
>
> Not for any particular gcc related reason I think, some dependent packages
> have static/shared builds, some don't.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #7 from Christoph Reiter ---
We currently link:
shared: gmp, winpthread, zlib, zstd
static: mpc, mpfr, isl
Not for any particular gcc related reason I think, some dependent packages have
static/shared builds, some don't.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #6 from Eric Botcazou ---
> So the rule of thumb is to never use -static-libgcc if you have a
> GCC-compiled DLL in the link, that's guaranteed to break otherwise.
So this could happen to the compiler if it is linked with the shared
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #5 from Eric Botcazou ---
> We do have some open bugs re broken exception handling with mingw32, like
> https://github.com/msys2/MINGW-packages/issues/9289#issuecomment-945306860
>
> Sadly no one stepped up to look into that. Do you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #4 from Christoph Reiter ---
I see, thanks for having a look :)
We do have some open bugs re broken exception handling with mingw32, like
https://github.com/msys2/MINGW-packages/issues/9289#issuecomment-945306860
Sadly no one stepp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
Eric Botcazou changed:
What|Removed |Added
Depends on||100486
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #2 from Christoph Reiter ---
Stack trace (I rebuilt the host gcc 11.3.0 with debug symbols and re-ran the
failing command with "-wrapper gdb,--args"):
Thread 1 received signal SIGSEGV, Segmentation fault.
0x7563bd90 in strlen () fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507
--- Comment #1 from Christoph Reiter ---
I've bisected it now:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=76f9c7f44fffb0b03266730b137313fe79f1c99e
76f9c7f44fffb0b03266730b137313fe79f1c99e is the first bad commit
commit 76f9c7f44fffb0b032667
11 matches
Mail list logo
