public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com> To: jason@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/10336: [3.3/3.4 regression] ICE with -Wunreachable-code Date: Tue, 15 Apr 2003 03:36:00 -0000 [thread overview] Message-ID: <20030415033601.14992.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/10336; it has been noted by GNATS. From: Jason Merrill <jason@redhat.com> To: steven@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, reichelt@igpm.rwth-aachen.de, gcc-gnats@gcc.gnu.org Subject: Re: middle-end/10336: [3.3/3.4 regression] ICE with -Wunreachable-code Date: Tue, 15 Apr 2003 04:28:24 +0100 --=-=-= Thanks, I'm testing this patch now. Yours leaves insn null for testcases that were crashing, so we wouldn't ever warn. --=-=-= Content-Type: text/x-patch Content-Disposition: inline *** jump.c.~2~ 2003-04-03 18:54:32.000000000 -0500 --- jump.c 2003-04-14 22:48:49.000000000 -0400 *************** never_reached_warning (avoided_insn, fin *** 1913,1919 **** us the head of a block, a NOTE_INSN_BASIC_BLOCK, which often follows the line note. */ for (insn = PREV_INSN (avoided_insn); ; insn = PREV_INSN (insn)) ! if (GET_CODE (insn) != NOTE) { insn = NEXT_INSN (insn); break; --- 1913,1920 ---- us the head of a block, a NOTE_INSN_BASIC_BLOCK, which often follows the line note. */ for (insn = PREV_INSN (avoided_insn); ; insn = PREV_INSN (insn)) ! if (GET_CODE (insn) != NOTE ! || NOTE_LINE_NUMBER (insn) == NOTE_INSN_FUNCTION_BEG) { insn = NEXT_INSN (insn); break; --=-=-=--
next reply other threads:[~2003-04-15 3:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-15 3:36 Jason Merrill [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-30 17:42 jason 2003-04-29 18:46 Wolfgang Bangerth 2003-04-15 6:36 Steven Bosscher 2003-04-12 12:49 steven
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=20030415033601.14992.qmail@sources.redhat.com \ --to=jason@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=jason@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).