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:57:00 -0000 [thread overview]
Message-ID: <bug-46878-4-ZKdhTwOpHS@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 #14 from Jeffrey A. Law <law at redhat dot com> 2011-01-22 00:50:25 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/21/11 17:41, dj at redhat dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46878
>
> --- Comment #12 from DJ Delorie <dj at redhat dot com> 2011-01-22 00:40:44 UTC ---
> Of course, one could argue that perhaps the compare should *not* have been
> removed? I don't know how clever the new redundant compare removal code is.
That's part of why I want a dump -- I seem to recall rules about
removing comparisons on cc0 machines and reading the dumps may help me
recall what those rules are.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNOim8AAoJEBRtltQi2kC7G5YIAIh7Nfv7ALDaKC3QwbKoqaXw
7zXr66Z1ephIXWQ/4eav6y7EXVapTl546ygOCjZg3IHEy2g0BJxwUzJk2vbIcbM9
1WnWQizMQdjGUcjSNtJsntoB5Yx7+xo4Y7ENeUct+yeQNPx19gkQ0H11mUuBY5ZV
Mqli07f0nzZ5dwWvdwoSngbYKMtgfYL6cIBsKVDvRPdHSGWH/27bcG0ExjCwTZsm
5AcVxRLrmD/FcqDXTW8sZEVyms0sEdmBb2v9eL6TlEqmzvVOZlSj2IjjNePYD4KY
O9VDU3ZgoHdrr8fzaW3ZsKyCrAwLVZZ1mYHeJt1nqnif64w4X++XRxZtlOGT1uM=
=S5Gb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-01-22 0:50 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
2011-01-22 3:57 ` law at redhat dot com [this message]
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-ZKdhTwOpHS@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: link
Be 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).