From: Janis Johnson <janis187@us.ibm.com>
To: gcc@gcc.gnu.org, jh@suse.cz
Subject: patch that caused regression PR f/9258
Date: Tue, 14 Jan 2003 20:59:00 -0000 [thread overview]
Message-ID: <20030114095503.A23671@us.ibm.com> (raw)
The regression reported in PR f/9258 ([3.2/3.3/3.4 regression] ICE in
compensate_edge, at reg-stack.c:2589) showed up with this patch:
Sat Jun 23 01:23:59 CEST 2001 Jan Hubicka <jh@suse.cz>
* flow.c (mark_set_1, attempt_auto_inc, mark_used_reg,
try_pre_increment_1): compute REG_FREQ using bb->frequency.
* regclass.c (loop_cost): Kill.
(frequency): New global variable.
(record_operand_costs): Replace loop_cost by frequency.
(scan_one_insn): Likewise.
(regclass): Likewise; set frequency according to bb->frequency.
* flow.c (split_edge): Set frequency.
I used the minimized test case from the PR and got the same ICE message.
This information has been added to the PR.
Janis
next reply other threads:[~2003-01-14 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 20:59 Janis Johnson [this message]
2003-01-14 21:13 ` Jan Hubicka
2003-01-14 22:05 ` Jan Hubicka
2003-01-15 8:49 ` Richard Henderson
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=20030114095503.A23671@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
/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).