From: Jan Hubicka <jh@suse.cz>
To: Richard Henderson <rth@redhat.com>,
Robert Myers <rmyers1400@attbi.com>, gcc <gcc@gcc.gnu.org>
Subject: Re: Feedback-driven optimization
Date: Sun, 23 Feb 2003 12:06:00 -0000 [thread overview]
Message-ID: <20030223110014.GB19895@kam.mff.cuni.cz> (raw)
In-Reply-To: <20030223091654.GA618@redhat.com>
> On Sun, Feb 23, 2003 at 02:04:38AM -0500, Robert Myers wrote:
> > One problem: my instincts tell me I should be working with RTL, not
> > binary, but gcc doesn't permit routine dump of RTL.
>
> Nope. You'll have to make your modifications within gcc itself.
Also there is already support for profile feedback in number of
optimizers. I am not sure how much more can be done in IA-64 specific
way - probably ifcvt can be made to use it better (there are papers
about profile based hyperblock formation, perhaps it is worthwhile to
implement this) and scheduler - there is already code for trace
schedling but it is not done on IA-64 compilation path as it does
scheduling. The modification would be trivial. I would be greatly
interested in results of these.
Honza
>
> > Another problem: I don't have an IA-64 and probably don't want one.
> > What I really want is an emulator that can be completely instrumented.
>
> There isn't a free ia64 simulator. To my knowledge, there isn't
> even a closed source simulator that is generally available.
>
>
> r~
next prev parent reply other threads:[~2003-02-23 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 9:16 Robert Myers
2003-02-23 11:00 ` Richard Henderson
2003-02-23 12:06 ` Jan Hubicka [this message]
2003-02-24 2:47 ` Robert Myers
2003-02-24 23:17 ` Jim Wilson
2003-02-24 1:16 Robert Dewar
2003-02-24 2:48 ` Robert Myers
2003-02-24 5:06 Robert Dewar
2003-02-24 11:16 Jakob Engblom
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=20030223110014.GB19895@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=rmyers1400@attbi.com \
--cc=rth@redhat.com \
/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).