public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46878] V850 ICE in in maybe_add_or_update_dep_1, at sched-deps.c:854 Date: Sat, 22 Jan 2011 03:46:00 -0000 [thread overview] Message-ID: <bug-46878-4-p02xxWJ5oF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46878-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46878 --- Comment #13 from Jeffrey A. Law <law at redhat dot com> 2011-01-22 00:42:52 UTC --- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/21/11 17:38, dj at redhat dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46878 > > --- Comment #11 from DJ Delorie <dj at redhat dot com> 2011-01-22 00:37:35 UTC --- > I set a breakpoint on the delete of that insn; at that time, the following insn > did not have the /S set on it. At the time when the /S is added, the previous > insn had already been deleted. So, it's delete first, set /s second, crash > third. OK. That means one of two things. Either the comparison shouldn't have been deleted or we shouldn't have added SCHED_GROUP_P to the setcc. > > And it's not the setcc that's delted, it's the (compare) before it. The setcc > is the one with the /s on it. I know. Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNOif2AAoJEBRtltQi2kC7tmQH/3BQml/X2yyb1QZpVr5jYNE7 e8f1StC+ktqaBgSr2nrclg/uIj8LontEPU+oOY3r9Ee56TWnBAVIe1b7nJ1H0MmX Kbfw1zFR5/xABoiOZiiAqGEulLiJpFEiC9yaucpQZBkUDjCKP/Lzt6xknuBKUxdJ IBIhNOQjBeFtopV0L88N2QfhLGiaV05RIbqVQHnYG6ti7GK0RErWP+jh14WaLPtV i0BcQ+2gzGKhBXLUS4BXC8O/T0ft87/uOhOp2O0u5v1j0zxS+dCcAVyGGKaDCDbs 8OCuOaYPDn52KH0YeQmVsQgexDLG21DrWr8QSzaLw8qkYg00XpM27xT6kZf9Yac= =8vRi -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-01-22 0:43 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-10 0:48 [Bug target/46878] New: " monaka@monami-software.com 2010-12-10 0:53 ` [Bug target/46878] " monaka@monami-software.com 2010-12-10 1:47 ` monaka@monami-software.com 2010-12-10 2:36 ` monaka@monami-software.com 2010-12-10 15:02 ` monaka@monami-software.com 2011-01-18 8:15 ` dj at redhat dot com 2011-01-18 13:50 ` law at redhat dot com 2011-01-18 13:56 ` law at redhat dot com 2011-01-21 22:39 ` dj at redhat dot com 2011-01-21 22:41 ` dj at redhat dot com 2011-01-22 0:43 ` law at redhat dot com 2011-01-22 0:50 ` law at redhat dot com 2011-01-22 1:11 ` dj at redhat dot com 2011-01-22 2:49 ` dj at redhat dot com 2011-01-22 3:46 ` law at redhat dot com [this message] 2011-01-22 3:57 ` law at redhat dot com 2011-01-22 9:40 ` law at redhat dot com 2011-01-26 0:09 ` dj at redhat dot com 2011-01-26 14:15 ` law at redhat dot com 2011-01-26 14:20 ` law at redhat dot com 2011-01-26 14:20 ` law at redhat dot com 2011-01-26 14:26 ` [Bug rtl-optimization/46878] " law at redhat dot com 2011-01-26 15:05 ` [Bug rtl-optimization/46878] [4.6 regression] " mikpe at it dot uu.se 2011-01-26 16:43 ` law at redhat dot com 2011-01-26 22:39 ` dj at gcc dot gnu.org 2011-01-27 1:25 ` dj at redhat dot com 2011-02-02 18:12 ` dnovillo 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-46878-4-p02xxWJ5oF@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).