public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24232] [4.1 Regression] ICE: segmentation fault in sched-ebb.c:220 add_missing_bbs
Date: Wed, 12 Oct 2005 03:07:00 -0000	[thread overview]
Message-ID: <20051012030717.1697.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24232-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from wilson at gcc dot gnu dot org  2005-10-12 03:07 -------
Created an attachment (id=9975)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9975&action=view)
Untested patch to fix problems with dependency serialization.

This adds an UNCOND argument to add_dependence_list, so that all structural
dependencies can be made unconditionally.  Examples of structural dependencies
are serialization dependencies on last_pending_memory_flush, dependencies added
to preserve REG_N_CALLS_CROSSED==0, and dependencies for clobbers.  All other
dependencies are still created only if the two instructions are not mutex.

This also eliminates some redundant JUMP_INSN dependency handling, as both
sched_analyze and sched_analyze_insn were creating dependencies for JUMP_INSNs.
 I deleted the former one.

This also stops trying to treat last_pending_memory_flush as a list.  It can
not function both as a list and as a serialization point.

This patch effectively makes pending_flush_length obsolete, but I can't delete
it because sched-rgn.c is using it in a strange way I don't understand.

This patch probably makes more dependencies than is necessary or desirable, but
some development work will be needed to fix that.  I believe that we can keep a
list of pending branch insns by keeping a list parallel to the pending read and
pending write lists.  This would help reduce the number of dependencies, and
help with cross block scheduling.  This will be a bit of work though, and may
not be reasonable to attempt at this late point.


-- 

wilson at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #9960 is|0                           |1
           obsolete|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24232


  parent reply	other threads:[~2005-10-12  3:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 10:27 [Bug rtl-optimization/24232] New: " rguenth at gcc dot gnu dot org
2005-10-06 10:28 ` [Bug rtl-optimization/24232] " rguenth at gcc dot gnu dot org
2005-10-06 10:33 ` rguenth at gcc dot gnu dot org
2005-10-06 10:46 ` rguenth at gcc dot gnu dot org
2005-10-06 10:58 ` rguenth at gcc dot gnu dot org
2005-10-06 13:25 ` [Bug target/24232] " pinskia at gcc dot gnu dot org
2005-10-06 13:28 ` [Bug target/24232] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-06 17:20 ` pinskia at gcc dot gnu dot org
2005-10-11  3:20 ` wilson at gcc dot gnu dot org
2005-10-11  6:20 ` wilson at specifix dot com
2005-10-11  6:26 ` wilson at specifix dot com
2005-10-12  2:52 ` wilson at gcc dot gnu dot org
2005-10-12  3:07 ` wilson at gcc dot gnu dot org [this message]
2005-10-15 16:34 ` cvs-commit at gcc dot gnu dot org
2005-10-15 16:55 ` wilson at gcc dot gnu dot org
2005-10-15 16:56 ` wilson at gcc dot gnu dot org
2005-10-15 17:26 ` steven at gcc dot gnu dot org
2005-10-15 17:29 ` steven at gcc dot gnu dot 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=20051012030717.1697.qmail@sourceware.org \
    --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).