From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: gcc@gcc.gnu.org
Subject: Problem with tree-ssa-loop-ivopts.c:get_computation-cost
Date: Thu, 30 Jun 2005 22:16:00 -0000 [thread overview]
Message-ID: <10506302218.AA00728@vlsi1.ultra.nyu.edu> (raw)
This function generates RTL from an expression to see how many RTL insns
it is. But this causes a problem compiling the Ada ACATS test cxa4006.
The problem is when part of the expression has a location. In that
case, record_block_change is called and that relies on
cfun->ib_boundaries_block being set. But it isn't because we aren't
expanding stuff "for real". A kludge would be to test that field, but
what's the proper way?
Also, seq_cost really should be looking at next_real_insn, not NEXT_INSN,
since any notes shouldn't be counted.
next reply other threads:[~2005-06-30 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 22:16 Richard Kenner [this message]
2005-07-05 8:32 ` Laurent GUERBY
2005-07-12 10:04 ` PR22336 (was: Problem with tree-ssa-loop-ivopts.c:get_computation-cost) Laurent GUERBY
2005-07-12 11:04 ` Zdenek Dvorak
2005-07-21 22:08 ` 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=10506302218.AA00728@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@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).