From: "Dave Korn" <dave.korn@artimi.com>
To: "'Dan Kegel'" <dank@kegel.com>, "'GCC Mailing List'" <gcc@gcc.gnu.org>
Subject: RE: [GCC 4.2 Project] Omega data dependence test
Date: Mon, 08 Aug 2005 16:27:00 -0000 [thread overview]
Message-ID: <SERRANOivwNMB0pNayW0000011f@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <42F77CFF.6040606@kegel.com>
----Original Message----
>From: Dan Kegel
>Sent: 08 August 2005 16:41
> Sebastian Pop wrote:
> > [http://gcc.gnu.org/wiki/Omega%20data%20dependence%20test]
> > ...
> I can't understand a word of the proposal.
Well, I'll pitch in, because I also wasn't sure at first whether it was
for real and what it was about, but I think I know now. Did you google
"bill pugh omega solver" and do some background reading? It didn't take me
too long to get the basic gist of what they're proposing (or at any rate, to
_think_ I had got it!).
IIUIC, they want to use a linear-algorithm solver to verify the
data-dependence analyses performed by the Bannerjee analyzer by recomputing
the results from an alternative formulation so as to have a 'second opinion'
to compare the output of gcc's current analyses against.[*]
> Mabe you were trying to be funny, but it ended up being obscure.
Although the last paragraph was purely tongue-in-cheek humour, the rest
looks genuine. But by the time it gets to the bit about SEB and POP, I
think it's just referring to Seb Pop!
> If the average gcc developer can understand it, then
> it doesn't matter that I can't, but I have a feeling
> others might find it hard to read, too.
The more esoteric fields of compiler design just _are_ incredibly dense,
theoretical, and hard-to-comprehend without spending a few years at
university studying them. Unfortunately, that's just the way it is.
cheers,
DaveK
[*] - To a first approximation. ;)
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-08-08 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 15:51 Dan Kegel
2005-08-08 16:12 ` Daniel Berlin
2005-08-08 16:27 ` Dave Korn [this message]
2005-08-08 18:39 ` Sebastian Pop
2005-08-08 18:31 ` Sebastian Pop
2005-08-08 22:48 ` Joe Buck
2005-08-09 14:55 ` Sebastian Pop
2005-08-09 16:23 ` Joe Buck
2005-08-13 23:07 ` Sebastian Pop
2005-08-14 1:36 ` Daniel Berlin
2005-08-14 11:10 ` Sebastian Pop
2005-08-14 15:40 ` Daniel Berlin
2005-08-14 1:49 ` Ian Lance Taylor
2005-08-09 22:57 ` Daniel Berlin
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 22:14 Daniel Kegel
2005-08-09 18:01 Daniel Kegel
2005-08-09 18:03 ` Andrew Pinski
2005-08-08 12:29 Sebastian Pop
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=SERRANOivwNMB0pNayW0000011f@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=dank@kegel.com \
--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).