public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" [not found] <bug-93758-4@http.gcc.gnu.org/bugzilla/> @ 2021-07-18 7:34 ` pinskia at gcc dot gnu.org 2021-07-18 7:34 ` pinskia at gcc dot gnu.org ` (2 subsequent siblings) 3 siblings, 0 replies; 4+ messages in thread From: pinskia at gcc dot gnu.org @ 2021-07-18 7:34 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://trac.macports.org/t | |icket/60091 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >during GIMPLE pass: ccp /path/to/gcc-9.2.0/libgfortran/generated/norm2_r4.c: In function ‘norm2_r4’: /path/to/gcc-9.2.0/libgfortran/generated/norm2_r4.c:213:1: internal compiler error: Segmentation fault: 11 I am 99% sure this is GMP/MPFR being miscompiled or compiled with the wrong options and not able to run on your host. Yes that is exactly what the macports ticket says: https://trac.macports.org/ticket/60091#comment:13 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" [not found] <bug-93758-4@http.gcc.gnu.org/bugzilla/> 2021-07-18 7:34 ` [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" pinskia at gcc dot gnu.org @ 2021-07-18 7:34 ` pinskia at gcc dot gnu.org 2021-07-18 12:14 ` mojca at macports dot org 2021-07-18 13:23 ` iains at gcc dot gnu.org 3 siblings, 0 replies; 4+ messages in thread From: pinskia at gcc dot gnu.org @ 2021-07-18 7:34 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So invalid. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" [not found] <bug-93758-4@http.gcc.gnu.org/bugzilla/> 2021-07-18 7:34 ` [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" pinskia at gcc dot gnu.org 2021-07-18 7:34 ` pinskia at gcc dot gnu.org @ 2021-07-18 12:14 ` mojca at macports dot org 2021-07-18 13:23 ` iains at gcc dot gnu.org 3 siblings, 0 replies; 4+ messages in thread From: mojca at macports dot org @ 2021-07-18 12:14 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758 --- Comment #4 from Mojca Miklavec <mojca at macports dot org> --- I'm sorry, I forgot about this ticket. I can confirm that building (version 11.1) in fact works on all macOS versions at the moment https://ports.macports.org/port/x86_64-w64-mingw32-gcc/details/ It's only broken for i686 on 10.6, but that's a completely different issue that we need to investigate separately at some point. (ld: illegal text-relocation to ___stdoutp in /usr/lib/libSystem.dylib from _main in build/gengenrtl.o for architecture i386) ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" [not found] <bug-93758-4@http.gcc.gnu.org/bugzilla/> ` (2 preceding siblings ...) 2021-07-18 12:14 ` mojca at macports dot org @ 2021-07-18 13:23 ` iains at gcc dot gnu.org 3 siblings, 0 replies; 4+ messages in thread From: iains at gcc dot gnu.org @ 2021-07-18 13:23 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758 --- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Mojca Miklavec from comment #4) > I'm sorry, I forgot about this ticket. I can confirm that building (version > 11.1) in fact works on all macOS versions at the moment > > https://ports.macports.org/port/x86_64-w64-mingw32-gcc/details/ > > It's only broken for i686 on 10.6, but that's a completely different issue > that we need to investigate separately at some point. > > (ld: illegal text-relocation to ___stdoutp in /usr/lib/libSystem.dylib from > _main in build/gengenrtl.o for architecture i386) Is that using clang as the bootstrap compiler? I have a patch that works around the issue with -m32 -fno-PIE producing broken relocations with clang - but I thought Ken had already applied it? ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-07-18 13:23 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-93758-4@http.gcc.gnu.org/bugzilla/>
2021-07-18 7:34 ` [Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault" pinskia at gcc dot gnu.org
2021-07-18 7:34 ` pinskia at gcc dot gnu.org
2021-07-18 12:14 ` mojca at macports dot org
2021-07-18 13:23 ` iains at gcc dot gnu.org
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).