From: Vladimir Makarov <vmakarov@redhat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Interesting paper from Perdue
Date: Tue, 21 Sep 2004 16:01:00 -0000 [thread overview]
Message-ID: <41504A34.2090409@redhat.com> (raw)
In-Reply-To: <7347164.1095676587061.SLOX.WebMail.wwwrun@extimap.suse.de>
Steven Bosscher wrote:
>I don't know if anyone has ever seen/read/mentioned this paper
>before, I might have missed it. Otherwise, interesting reading:
>https://engineering.purdue.edu/ECE/Research/TR/2004pdfs/TR-ECE-04-01.pdf
>
>
>
The most interesting thing about the article is that they spent a lot of
machine time (which I have no in my disposal) to investigate individual
options to get a better SPECInt2000 results.
But I see they used a black box approach because they don't know gcc
internals at all (they tried -fschedule-insns for p4 which does nothing,
they also did not use -mtune=pentium4, etc).
Their most complex algorithm (3rd algorithm) to choose better option
combination is just oversimplified taboo search algorithm (with list of
taboo moves which never expire). I think that an algorithm based on
taboo metaheuristic would achieve better results for the same number of
tries. Imho the taboo algorithm is the best fit approach for solution
of the task (genetic apporach used by Scott Ladd or more random
semulated annealing approach would work much worse on my opinion).
In any case, the approach is not practical (on my evaluation it needs
about 15 hours to choose options by the 3rd algorithm for one
SPECInt2000 test -- three 3 minutes runs, 20 options, 4 iteration as
they reported). Alhough it could be used to get a better (peak)
SPECInt2000 report.
Vlad
prev parent reply other threads:[~2004-09-21 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 13:31 Steven Bosscher
2004-09-21 7:21 ` tm_gccmail
2004-09-21 17:59 ` Vladimir Makarov
2004-09-21 18:39 ` Daniel Berlin
2004-09-21 16:01 ` Vladimir Makarov [this message]
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=41504A34.2090409@redhat.com \
--to=vmakarov@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=stevenb@suse.de \
/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).