public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc@Denis-Excoffier.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/60830] New: ICE on bootstrapping on cygwin Date: Sun, 13 Apr 2014 10:28:00 -0000 [thread overview] Message-ID: <bug-60830-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60830 Bug ID: 60830 Summary: ICE on bootstrapping on cygwin Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: gcc@Denis-Excoffier.org Installed gcc-4.9.0-RC-20140411 on darwin (Mavericks) with no problem. But: On Cygwin 1.7.29-2 (+ latests patches), platform=i686-pc-cygwin (Windows XP SP3, 32 bits), bootstrap stops with: xgcc: internal compiler error: Segmentation fault (program cc1) Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. configure: error: in `/tmp/lcl/tmp/gcc/obj/i686-pc-cygwin/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. make[2]: *** [configure-stage2-target-libgcc] Error 1 make[1]: *** [stage2-bubble] Error 2 make: *** [all] Error 2 Indeed, inside /tmp/lcl/tmp/obj/gcc: % echo "int main() { return 0; }" > foo.c % cc1 -quiet -o foo.c foo.c foo.c:1:1: internal compiler error: Aborted int main() { return 0; } ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. % The foo.o seems ok. After some investigation, it seems that cc1 receives an unexpected SIGABRT signal, after the end of main(), and strace confirms the kill: % strace -o /tmp/1 cc1 -quiet -o foo.o foo.c (same messages as above) % cat /tmp/1 ... 344 4823227 [main] cc1 3768 close: 0 = close(3) 2019 4825246 [main] cc1 3768 set_signal_mask: setmask 0, newmask FFFEFEDK, mask_bits 0 23 4825269 [main] cc1 3768 kill0: kill (3768, 6) 22 4825291 [main] cc1 3768 sig_send: sendsig 0x784, pid 3768, signal 6, its_me 1 ... % On the other hand, if foo.c is erroneous, all seems ok: % echo "it main() { return 0; }" > foo.c foo.c:1:1: error: unknown type name 'it' it main() { return 0; } ^ foo.c:1: confused by earlier errors, bailing out % I don't know what to do next.
next reply other threads:[~2014-04-13 10:28 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-13 10:28 gcc@Denis-Excoffier.org [this message] 2014-04-13 11:05 ` [Bug bootstrap/60830] " gcc@Denis-Excoffier.org 2014-04-13 12:33 ` mikpelinux at gmail dot com 2014-04-14 8:44 ` [Bug bootstrap/60830] [4.9 Regression] " rguenth at gcc dot gnu.org 2014-04-14 8:45 ` rguenth at gcc dot gnu.org 2014-04-14 9:05 ` gcc@Denis-Excoffier.org 2014-04-14 9:06 ` gcc@Denis-Excoffier.org 2014-04-14 9:11 ` gcc@Denis-Excoffier.org 2014-04-14 14:16 ` jakub at gcc dot gnu.org 2014-04-14 14:42 ` gcc@Denis-Excoffier.org 2014-04-14 14:43 ` gcc@Denis-Excoffier.org 2014-04-14 17:06 ` ktietz at gcc dot gnu.org 2014-04-14 18:54 ` ktietz at gcc dot gnu.org 2014-04-15 9:35 ` gcc@Denis-Excoffier.org 2014-04-15 9:35 ` gcc@Denis-Excoffier.org 2014-04-15 9:59 ` ktietz at gcc dot gnu.org 2014-04-15 10:04 ` rguenth at gcc dot gnu.org 2014-04-15 10:31 ` ktietz at gcc dot gnu.org 2014-04-15 12:19 ` ktietz at gcc dot gnu.org 2014-04-15 16:20 ` gcc@Denis-Excoffier.org 2014-04-15 16:31 ` gcc@Denis-Excoffier.org 2014-04-15 16:50 ` gcc@Denis-Excoffier.org 2014-04-16 7:38 ` gcc@Denis-Excoffier.org 2014-04-16 12:10 ` ktietz at gcc dot gnu.org 2014-04-18 12:37 ` gcc@Denis-Excoffier.org 2014-04-18 19:37 ` bernd.edlinger at hotmail dot de 2014-04-20 19:09 ` bernd.edlinger at hotmail dot de 2014-04-21 14:02 ` bernd.edlinger at hotmail dot de 2014-04-21 16:31 ` gcc@Denis-Excoffier.org 2014-04-21 16:35 ` gcc@Denis-Excoffier.org 2014-04-21 16:50 ` bernd.edlinger at hotmail dot de 2014-04-21 17:01 ` gcc@Denis-Excoffier.org 2014-04-21 17:18 ` bernd.edlinger at hotmail dot de 2014-04-21 17:40 ` gcc@Denis-Excoffier.org 2014-04-21 17:52 ` ktietz at gcc dot gnu.org 2014-04-21 20:40 ` bernd.edlinger at hotmail dot de 2014-04-21 20:48 ` bernd.edlinger at hotmail dot de 2014-04-22 7:24 ` ktietz at gcc dot gnu.org 2014-04-22 7:29 ` bernd.edlinger at hotmail dot de 2014-04-22 7:38 ` gcc@Denis-Excoffier.org 2014-04-22 13:50 ` gcc@Denis-Excoffier.org 2014-04-27 14:10 ` mikpelinux at gmail dot com 2014-04-30 14:23 ` ktietz at gcc dot gnu.org 2014-05-02 17:36 ` fanael4 at gmail dot com 2014-05-02 19:50 ` bernd.edlinger at hotmail dot de 2014-07-13 10:34 ` gcc@Denis-Excoffier.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-60830-4@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).