Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS]  Fwd: Old and Tradition was V9 shell
Date: Mon, 24 Feb 2020 11:19:33 -0500	[thread overview]
Message-ID: <CAC20D2OxJ4otz8aQ=EK2zR08t8dhZecQVoZ5EZd3k5yhx1fnnQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Pag=Gt-SwoQSoz+KH10kMTm45Nx+T=M0QNjS+ODEa69w@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3752 bytes --]

I probably should have added, it's not just the learnings from DEC Gem
folks, but also the old "Kuck and Associates" team formerly in Champaign
(Intel moved them all to Austin).

On Mon, Feb 24, 2020 at 11:15 AM Clem Cole <clemc at ccc.com> wrote:

>
> First please continue this discussion on COFF (which has been CC'ed).
> While Fortran is interesting to many, it not a UNIX topic per say.
>
> Also, as I have noted in other places, I work for Intel - these comments
> are my own and I'm not trying to sell you anything.  Just passing on 45+
> years of programming experience.
>
> On Mon, Feb 24, 2020 at 10:34 AM Adam Thornton <athornton at gmail.com>
> wrote:
>
>> I would think that FORTRAN is likelier to be passed around as folk wisdom
>> and ancient PIs (uh, Primary Investigators, not the detective kind)
>> thrusting a dog-eared FORTRAN IV manual at their new grad students and
>> snarling "RTFM!" than as actual college courses.
>>
> FWIW: I was at CMU last week recruiting.  Fortran, even at a leading CS
> place like CMU, is hardly "folk wisdom". All the science PhD's (Chem, Mat
> Sci, Bio, Physics) that I interviewed all knew and used Fortran (nad listed
> on their CV's) as their primary language for their science.
>
> As I've quipped before, Fortran pays my own (and a lot of other people's
> salaries in the industry).  Check out:
> https://www.archer.ac.uk/status/codes/ Fortran is about 90% of the codes
> running (FWIW:  I have seen similar statistics from other large HPC sites
> - you'll need to poke).
>
> While I do not write in it, I believe there are three reasons why these
> statistics are true and* going to be true for a very long time*:
>
>    1. The math being used has not changed.  Just open up the codes and
>    look at what they are doing.  You will find that they all are all solving
>    systems of partial differential equations using linear algebra (-- see the
>    movie:  "Hidden Figures").
>    2. 50-75 years of data sets with know qualities and programs to work
>    with them.  If you were able to replace the codes magically with something
>    'better' - (from MathLab to Julia or Python to Java) all their data would
>    have to be requalified (it is like the QWERTY keyboard - that shipped
>    sailed years ago).
>    3. The *scientists want to do their science* for their work to get
>    their degree or prize.   The computer and its programs *are a tool*
>    for them look at data *to do their science*.   They don't care as long
>    as they get their work done.
>
>
> Besides Adam's mention of flang, there is, of course, gfortran; but there
> are also commerical compilers available for use:  Qualify for Free
> Software | Intel® Software
> <https://software.intel.com/en-us/articles/qualify-for-free-software>  I
> believe PGI offers something similar, but I have not checked in a while.
> Most 'production' codes use a real compiler like Intel, PGI or Cray's.
>
> FWIW: the largest number of LLVM developers are at Intel now.  IMO,
> while flang is cute, it will be a toy for a while, as the LLVM IL really
> can not handle Fortran easily.  There is a huge project to put a number of
> the learnings from the DEC Gem compilers into LLVM and one piece is gutting
> the internal IL and making work for parallel architectures.  The >>hope<<
> by many of my peeps, (still unproven) is that at some point the FOSS world
> will produce a compiler as good a Gem or the current Intel icc/ifort set.
> (Hence, Intel is forced to support 3 different compiler technologies
> internally in the technical languages group).
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200224/7f99a23f/attachment-0001.html>


  reply	other threads:[~2020-02-24 16:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 18:41 [COFF] Old and Tradition was [TUHS] " clemc
     [not found] ` <CAP2nic2C4-m_Epcx7rbW2ssbS850ZFiLKiL+hg1Wxbcwoaa1vQ@mail.gmail.com>
2020-02-12  0:57   ` [COFF] Fwd: " athornton
2020-02-12  1:58     ` clemc
2020-02-12  3:01       ` lm
2020-02-12 18:12         ` clemc
2020-02-12 21:55           ` cym224
2020-02-12 22:11           ` imp
2020-02-12 22:45             ` sauer
2020-02-12 23:05               ` lm
2020-02-12 23:54                 ` [COFF] floating point (Re: " bakul
2020-02-12 23:56                   ` bakul
2020-02-13  1:21                   ` toby
2020-02-13  6:57             ` [COFF] Fwd: " peter
2020-02-16 21:47           ` wobblygong
2020-02-16 22:10             ` clemc
2020-02-16 22:45               ` krewat
2020-02-16 23:50               ` bakul
2020-02-18  0:17                 ` dave
2020-02-18 12:48                   ` jpl.jpl
2020-02-24  9:40         ` ik
2020-02-24 15:19           ` lm
     [not found]             ` <CAP2nic0fK+=eh=5MuY4BJH6zx4tCRMWcazmm1khYMzNmEdf8ug@mail.gmail.com>
2020-02-24 16:15               ` [COFF] [TUHS] Fwd: Old and Tradition was " clemc
2020-02-24 16:19                 ` clemc [this message]
2020-02-24 16:27             ` [COFF] Fwd: Old and Tradition was [TUHS] " clemc

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='CAC20D2OxJ4otz8aQ=EK2zR08t8dhZecQVoZ5EZd3k5yhx1fnnQ@mail.gmail.com' \
    --to=coff@minnie.tuhs.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 NNTP newsgroup(s).