From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: Entry for the LITERATURE
Date: Fri, 07 Nov 1997 09:14:00 -0000 [thread overview]
Message-ID: <9711071609.AA02335@moene.indiv.nluug.nl> (raw)
I just came across this jewel:
*** QUOTE ***
From: metcalf@mail.cern.ch (Mike METCALF)
Organization: CERN - European Organization for Nuclear Research
Subject: XLF - all is revealed
Date: Thu, 6 Nov 1997 14:12:21 GMT
Newsgroups: comp.lang.fortran
There are often discussions/speculations here about how given
compilers optimize source code, and in particular about how they
deal with optimal use of cache memory. I have just noticed a paper
describing exactly how this is done in IBM's xlf compiler, using the
-qhot option, as of version 4. The reference is: IBM J. Res.
Develop., 41, 3, May 1997, 233-264 - Automatic selection of
high-order transformations in the IBM XL Fortran compiler, V.
Sarkar.
Highly recommended.
Mike Metcalf
*** UNQUOTE ***
Mike Metcalf is a long time (i.e. since mid-60's) CERN scientist
who has been on various Fortran Standardisation bodies.
I hope this paper saves me a lot of explaining my `after the
release' wish-list for Fortran specific optimisations :-)
David (Edelsohn), is this paper online somewhere ?
Cheers,
Toon.
next reply other threads:[~1997-11-07 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-07 9:14 Toon Moene [this message]
1997-11-07 11:15 ` David Edelsohn
1997-11-08 21:12 ` Jeffrey A Law
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=9711071609.AA02335@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=egcs@cygnus.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).