public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64284] [5 Regression] ICE: Segmentation fault Date: Fri, 12 Dec 2014 11:20:00 -0000 [thread overview] Message-ID: <bug-64284-4-Scn7OOhqGD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64284-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64284 --- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- trippels@gcc20 ~ % cat scp.i int *a; int b; int fn1() { enum { QSTRING } c = 0; while (1) { switch (*a) { case '\'': c = 0; default: switch (c) case 0: if (b) return 0; c = 1; } a++; } }
next prev parent reply other threads:[~2014-12-12 11:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-12 11:01 [Bug tree-optimization/64284] New: " rguenth at gcc dot gnu.org 2014-12-12 11:02 ` [Bug tree-optimization/64284] " rguenth at gcc dot gnu.org 2014-12-12 11:19 ` rguenth at gcc dot gnu.org 2014-12-12 11:20 ` trippels at gcc dot gnu.org [this message] 2014-12-12 11:45 ` rguenth at gcc dot gnu.org 2014-12-15 8:20 ` rguenth at gcc dot gnu.org 2014-12-15 8:20 ` rguenth at gcc dot gnu.org 2015-03-05 14:28 ` yroux 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-64284-4-Scn7OOhqGD@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).