public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ncahill_alt at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53262] New: ICE compiling busybox 1.19.3 with gcc 4.7.0 Date: Mon, 07 May 2012 10:11:00 -0000 [thread overview] Message-ID: <bug-53262-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53262 Bug #: 53262 Summary: ICE compiling busybox 1.19.3 with gcc 4.7.0 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: ncahill_alt@yahoo.com This code produces an internal compiler error with gcc 4.7.0. Build it with this command: gcc -O2 -o a a.c. This is gcc built from the original 4.7.0 source, x86 32-bit. **** a.c ****** typedef unsigned int size_t; enum { _ISalnum = 1 }; extern __const unsigned short int **__ctype_b_loc (void) __attribute__ ((__nothrow__)) __attribute__ ((__const)); void parse_config_file(char *map, size_t len) { char *end_3 = map + len - 3; char *end_7 = map + len - 7; char *p = map; char *q; int off; for (; p <= end_3; p++) { if (!(((*__ctype_b_loc ())[(int) ((*p))] & (unsigned short int) _ISalnum) || *p == '_')) continue; if (p < end_7 && p[6] == '_') { if (!memcmp(p, "CONFIG", 6)) goto conf7; } continue; conf7: off = 7; for (q = p; q < end_3+3; q++) {} if (q != p) { use_config(p, q-p); } } } ***** end a.c **** a.c: In function 'parse_config_file': a.c:28:10: internal compiler error: Segmentation fault Thank you. Neil Cahill.
next reply other threads:[~2012-05-07 10:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-07 10:11 ncahill_alt at yahoo dot com [this message] 2012-05-07 11:18 ` [Bug c/53262] " rguenth at gcc dot gnu.org 2012-05-07 18:39 ` [Bug middle-end/53262] " ncahill_alt at yahoo dot com 2012-05-08 10:20 ` rguenth 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-53262-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).