public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: jason@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/10336: [3.4 regression] ICE with -Wunreachable-code Date: Mon, 28 Apr 2003 22:36:00 -0000 [thread overview] Message-ID: <20030428223600.14734.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/10336; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: gcc-gnats@gcc.gnu.org, reichelt@igpm.rwth-aachen.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jason@gcc.gnu.org, bangerth@gcc.gnu.org Cc: Subject: Re: middle-end/10336: [3.4 regression] ICE with -Wunreachable-code Date: Tue, 29 Apr 2003 00:29:12 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10336 Jason, Your patch added this line: + for (insn = PREV_INSN (avoided_insn); ; insn = PREV_INSN (insn)) I fixed a bug some time ago where such a loop ignored BARRIER insns, walked the whole list of INSNs until insn was NULL, which caused a segfault. It seems that for this test case, the same thing happens in your new loop. You can see in gdb that the C front end is ignoring "(barrier 14 13 15)". Two insns later you have a the segfault... So maybe something like this would fix it?? + for (insn = PREV_INSN (avoided_insn); + GET_CODE (insn) != BARRIER; + insn = PREV_INSN (insn)) Assuming PREV_INSN (avoided_insn) is never NULL, but of course we make that assumption now, too. Can't test it this week. Wolfgang, maybe you can, and if it works, submit a patch and use your new privileges? :-) Greetz Steven
next reply other threads:[~2003-04-28 22:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-28 22:36 Steven Bosscher [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-29 17:46 Jason Merrill 2003-04-29 17:36 Giovanni Bajo 2003-04-29 17:26 Wolfgang Bangerth 2003-04-29 0:16 Wolfgang Bangerth 2003-04-28 17:59 bangerth
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=20030428223600.14734.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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).