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 00:43:00 -0000	[thread overview]
Message-ID: <bug-46878-4-0B2N1tOSFy@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 #9 from Jeffrey A. Law <law at redhat dot com> 2011-01-22 00:31:30 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/21/11 15:22, dj at redhat dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46878
> 
> DJ Delorie <dj at redhat dot com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |dj at redhat dot com
> 
> --- Comment #7 from DJ Delorie <dj at redhat dot com> 2011-01-21 22:21:48 UTC ---
> sched-deps:sched_analyze_2 has this:
> 
> #ifdef HAVE_cc0
>     case CC0:
>       /* User of CC0 depends on immediately preceding insn.  */
>       SCHED_GROUP_P (insn) = 1;
> 
> But the conditional before the setcc was deleted (that's insn 22).
> So the comment above is wrong in this case; there is no immediately preceeding
> insn.
When the conditional was deleted, was SCHED_GROUP_P set on the following
insn?

jeff

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNOiVEAAoJEBRtltQi2kC76uYH/0HO/T/PXYL4kSaGWolf3MIh
C2IyMaRqSRLtjVN1y2YGTF1JE8UezHwWv9rYY9NzgaIAFpBoCQ0QYK3fxJXz5pH8
2yEq64LsNcnlCSrNy8NKgdqc3l3a2KaiT4ZVwqsflPnrrxt3LZElx+zrdXOAz7Me
5GFsHOpG6PfOcd9WNwD+Os54Fx5UB8ooMk4DZFf30rHe6HUMJf0kvwHambAfLXXx
4AnEAz90iyUaFGK37rNxVRTlzk33rWaNA+8rJrA54IcqLN7Q8fCugAqp5xT2152r
+jDITL376B+vZB7J1HTnelgZ2fZvOOZkx0A7bh+QUablG3arkx06InMbRI+AhtE=
=k4Kp
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2011-01-22  0:32 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 [this message]
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
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-0B2N1tOSFy@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).