public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "je.suis.bon at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/57625] New: internal compiler error: seg fault when building gcc 4.7.2 Date: Sat, 15 Jun 2013 16:48:00 -0000 [thread overview] Message-ID: <bug-57625-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57625 Bug ID: 57625 Summary: internal compiler error: seg fault when building gcc 4.7.2 Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: major Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: je.suis.bon at googlemail dot com Created attachment 30308 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30308&action=edit libgcc2.c I was attempting to build gcc 4.7.2 using gcc 4.8.1. to reproduce: mkdir build-gcc cd build-gcc ../gcc-4.7.2/configure --disable-nls --enable-languages=c echo "MAKEINFO = :" >> Makefile # otherwise compile fails! make all-gcc make all-target-libgcc The following error occurs: ../../../../originalsrc/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2': ../../../../originalsrc/gcc-4.7.2/libgcc/libgcc2.c:273:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [_absvdi2.o] Error 1 In compliance with gcc's dying wishes, I have submitted a bug report. Although I'm sure you already have it, for rapid perusal, I have attached the source file that caused the seg fault. extra information: $gcc --version: gcc (GCC) 4.8.1 system: archlinux amd64, using the gcc package "gcc-4.8.1-1" If any further information is required, please ask.
next reply other threads:[~2013-06-15 16:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-15 16:48 je.suis.bon at googlemail dot com [this message] 2013-06-15 17:57 ` [Bug middle-end/57625] " pinskia at gcc dot gnu.org 2013-06-15 20:20 ` mikpe at it dot uu.se 2013-11-05 23:21 ` arapov at gmail dot com 2014-05-21 12:33 ` redi at gcc dot gnu.org 2014-05-21 21:52 ` mikpelinux at gmail dot com 2014-05-24 19:28 ` mikpelinux at gmail dot com 2014-05-25 10:30 ` mikpelinux at gmail dot com 2015-09-21 13:38 ` mpolacek 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-57625-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).