public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at bigpond dot net dot au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18718] [4.0 Regression] ICE: Segmentation fault in in schedule_region (rgn=0) at sched-rgn.c:2325
Date: Tue, 30 Nov 2004 03:25:00 -0000	[thread overview]
Message-ID: <20041130032531.29864.qmail@sourceware.org> (raw)
In-Reply-To: <20041129154628.18718.micis@gmx.de>


------- Additional Comments From amodra at bigpond dot net dot au  2004-11-30 03:25 -------
Obviously, the loop expects REG_SAVE_NOTEs in pairs, which it isn't getting,
hence the segfault.

This is because the function that adds these notes, sched_analyze, is being
called on basic blocks, and the NOTE_INSN_LOOP_BEG/END pair isn't in the same
basic block.  Smell like bit rot.

;; End of basic block 2, registers live:
 1 [1] 31 [31] 67 [ap] 123 124

(note:HI 48 22 23 NOTE_INSN_LOOP_BEG)

;; Start of basic block 3, registers live: 1 [1] 31 [31] 67 [ap] 123 124
(code_label:HI 23 48 24 3 4 "" [1 uses])

[snip]

;; Start of basic block 4, registers live: 1 [1] 31 [31] 67 [ap] 122 124
[snip]

(note:HI 49 34 63 4 NOTE_INSN_LOOP_END)

[snip]


-- 


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


  parent reply	other threads:[~2004-11-30  3:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 15:46 [Bug middle-end/18718] New: " micis at gmx dot de
2004-11-29 15:48 ` [Bug middle-end/18718] " micis at gmx dot de
2004-11-29 16:14 ` pinskia at gcc dot gnu dot org
2004-11-29 16:20 ` [Bug middle-end/18718] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-29 16:55 ` pinskia at gcc dot gnu dot org
2004-11-29 18:11 ` pinskia at gcc dot gnu dot org
2004-11-30  3:25 ` amodra at bigpond dot net dot au [this message]
2004-11-30  3:57 ` amodra at bigpond dot net dot au
2004-11-30  4:48 ` pinskia at gcc dot gnu dot org
2004-11-30  4:49 ` amodra at bigpond dot net dot au
2004-11-30 12:44 ` steven at gcc dot gnu dot org
2004-12-03 11:43 ` steven at gcc dot gnu dot org
2004-12-03 23:05 ` amodra at bigpond dot net dot au
2004-12-03 23:55 ` amodra at bigpond dot net dot au

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=20041130032531.29864.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).