public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/97499] build dos cross compiler ICE Date: Tue, 20 Oct 2020 00:18:11 +0000 [thread overview] Message-ID: <bug-97499-4-3cCiAComQ2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97499-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97499 --- Comment #1 from fdlbxtqi <euloanty at live dot com> --- /gcc_dos_build/./gcc/xgcc -B/gcc_dos_build/./gcc/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/bin/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/lib/ -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/include -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes -Wno-error=format-diag -Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -I. -I. -I../.././gcc -I../../../gcc/libgcc -I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc -I../../../gcc/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -Wno-missing-prototypes -Wno-type-limits -o fixunstfsi.o -MT fixunstfsi.o -MD -MP -MF fixunstfsi.dep -c ../../../gcc/libgcc/soft-fp/fixunstfsi.c ../../../gcc/libgcc/config/i386/sfp-exceptions.c: In function '__sfp_handle_exceptions': ../../../gcc/libgcc/config/i386/sfp-exceptions.c:71:7: internal compiler error: Segmentation fault 71 | float f = 1.0f, g = 0.0f; | ^~~~~ libbacktrace could not find executable to open Please submit a full bug report, with preprocessed sour/gcc_dos_build/./gcc/xgcc -B/gcc_dos_build/./gcc/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/bin/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/lib/ -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/include -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes -Wno-error=format-diag -Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -I. -I. -I../.././gcc -I../../../gcc/libgcc -I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc -I../../../gcc/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -Wno-missing-prototypes -Wno-type-limits -o floatsitf.o -MT floatsitf.o -MD -MP -MF floatsitf.dep -c ../../../gcc/libgcc/soft-fp/floatsitf.c ce if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. /gcc_dos_build/./gcc/xgcc -B/gcc_dos_build/./gcc/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/bin/ -B/i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/lib/ -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/include -isystem /i586-pc-msdosdjgpp/i586-pc-msdosdjgpp/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes -Wno-error=format-diag -Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -I. -I. -I../.././gcc -I../../../gcc/libgcc -I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc -I../../../gcc/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -Wno-missing-prototypes -Wno-type-limits -o floatunsitf.o -MT floatunsitf.o -MD -MP -MF floatunsitf.dep -c ../../../gcc/libgcc/soft-fp/floatunsitf.c make[1]: *** [../../../gcc/libgcc/static-object.mk:17: sfp-exceptions.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory '/gcc_dos_build/i586-pc-msdosdjgpp/libgcc' make: *** [Makefile:12394: all-target-libgcc] Error 2
next prev parent reply other threads:[~2020-10-20 0:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-20 0:17 [Bug bootstrap/97499] New: " euloanty at live dot com 2020-10-20 0:18 ` euloanty at live dot com [this message] 2020-10-20 6:03 ` [Bug bootstrap/97499] " rguenth at gcc dot gnu.org 2021-05-24 7:18 ` pinskia at gcc dot gnu.org
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-97499-4-3cCiAComQ2@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: linkBe 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).