From: Robert Myers <rmyers1400@attbi.com>
To: Robert Dewar <dewar@gnat.com>
Cc: jh@suse.cz, gcc@gcc.gnu.org, rth@redhat.com
Subject: Re: Feedback-driven optimization
Date: Mon, 24 Feb 2003 02:48:00 -0000 [thread overview]
Message-ID: <3E597263.3060709@attbi.com> (raw)
In-Reply-To: <20030224003405.CB870F2DE7@nile.gnat.com>
Robert Dewar wrote:
>>What I want to know is how much of the disappointing performance of VLIW
>>is fundamental: the information just isn't there, and how much is
>>pragmatic: the information might be there but no one can imagine putting
>>the effort in that would be necessary to exploit it.
>>
>>
>
>Many people have studied this question in great detail, so the first step for
>you is a major effort cracking the existing literature.
>
>
>
There's alot to read, and I've scanned a fair bit of it. No one seems
to have tried anything as ambitious as what I have in mind, which, is
given all the preconceptions and experience available, come up with a
best expected strategy. There are fairly straightforward recipes for
doing this, but I don't think anybody has actually tried them. What
people *have* done is to use profiling to identify areas for increased
scrutiny, but with only limited success.
RM
next prev parent reply other threads:[~2003-02-24 1:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 1:16 Robert Dewar
2003-02-24 2:48 ` Robert Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 11:16 Jakob Engblom
2003-02-24 5:06 Robert Dewar
2003-02-23 9:16 Robert Myers
2003-02-23 11:00 ` Richard Henderson
2003-02-23 12:06 ` Jan Hubicka
2003-02-24 2:47 ` Robert Myers
2003-02-24 23:17 ` Jim Wilson
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=3E597263.3060709@attbi.com \
--to=rmyers1400@attbi.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--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).