From: Andre Vehreschild <vehre@gmx.de>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: Benson Muite <benson_muite@emailplus.org>,
Damian Rouson <damian@archaeologic.codes>,
Jerry D <jvdelisle2@gmail.com>,
Mikael Morin <morin-mikael@orange.fr>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>,
GCC-Fortran-ML <fortran@gcc.gnu.org>,
Lexi Pimenidis <lexi@badgersystems.de>
Subject: Re: Possible funding of gfortran work
Date: Mon, 5 Jun 2023 14:21:19 +0200 [thread overview]
Message-ID: <20230605142119.5919b7df@vepi2> (raw)
In-Reply-To: <ec72a74c-ea99-e6ab-6612-afe95ec39a4c@netcologne.de>
I have referenced LAPACK now. I hope this is ok?
- Andre
On Mon, 5 Jun 2023 14:16:43 +0200
Thomas Koenig <tkoenig@netcologne.de> wrote:
> On 05.06.23 12:07, Andre Vehreschild wrote:
> >> R and Octave may also be good examples of use cases.
> > Mhhh, both are not written in Fortran, right?
>
> They are not, but at least R uses Lapack, which is written in Fortran.
> And Lapack is about as central to scientific computing as you can
> be.
>
> Best regards
>
> Thomas
--
Andre Vehreschild * Email: vehre ad gmx dot de
next prev parent reply other threads:[~2023-06-05 12:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 4:34 Jerry DeLisle
2023-05-26 17:09 ` Bernhard Reutner-Fischer
2023-05-26 21:22 ` Jerry D
2023-05-27 8:08 ` Thomas Koenig
2023-05-27 11:24 ` Andre Vehreschild
2023-05-27 16:19 ` Paul Richard Thomas
2023-05-28 14:26 ` Nicolas König
2023-05-28 15:07 ` Thomas Koenig
2023-05-28 19:25 ` Mikael Morin
2023-05-28 20:53 ` Jerry D
2023-05-30 13:32 ` Andre Vehreschild
2023-05-30 20:08 ` Thomas Koenig
2023-05-31 3:46 ` Benson Muite
2023-05-31 6:08 ` Thomas Koenig
2023-05-31 8:42 ` Benson Muite
2023-05-31 12:23 ` Andre Vehreschild
2023-05-31 14:08 ` Damian Rouson
2023-06-01 9:18 ` Andre Vehreschild
2023-06-01 10:56 ` Bernhard Reutner-Fischer
2023-06-01 10:59 ` Mikael Morin
2023-06-04 8:23 ` Thomas Koenig
2023-06-05 8:08 ` Andre Vehreschild
2023-06-05 11:44 ` Mikael Morin
2023-06-06 13:06 ` Andre Vehreschild
2023-06-08 12:38 ` Mikael Morin
2023-06-14 8:28 ` Andre Vehreschild
2023-06-14 9:40 ` Mikael Morin
2023-06-14 18:48 ` Bernhard Reutner-Fischer
2023-06-01 11:12 ` Benson Muite
2023-06-04 7:49 ` Thomas Koenig
2023-06-05 10:12 ` Andre Vehreschild
2023-06-05 10:07 ` Andre Vehreschild
2023-06-05 12:16 ` Thomas Koenig
2023-06-05 12:21 ` Andre Vehreschild [this message]
2023-06-08 5:34 ` Benson Muite
2023-06-14 8:00 ` Andre Vehreschild
2023-06-02 0:53 ` Jerry D
2023-06-05 10:09 ` Andre Vehreschild
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=20230605142119.5919b7df@vepi2 \
--to=vehre@gmx.de \
--cc=benson_muite@emailplus.org \
--cc=damian@archaeologic.codes \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
--cc=lexi@badgersystems.de \
--cc=morin-mikael@orange.fr \
--cc=paul.richard.thomas@gmail.com \
--cc=tkoenig@netcologne.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).