From: David Malcolm <dmalcolm@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [pushed] wwwdocs: readings: Remove Herman D. Knoble's Fortran Resources
Date: Wed, 01 Feb 2023 11:23:18 -0500 [thread overview]
Message-ID: <a34e82bda9cbf265e4b90e9db0f8b553685fe714.camel@redhat.com> (raw)
In-Reply-To: <20230201095624.AAF1633E9B@hamza.pair.com>
On Wed, 2023-02-01 at 10:56 +0100, Gerald Pfeifer wrote:
> The original page is gone, and search engines did not reveal a new
> location.
>
> If any of you has a new location, feel free to add that (or let me
> know and I'll take care).
FWIW the most recent version in archive.org is here:
https://web.archive.org/web/20220624224837/http://www.personal.psu.edu/faculty/h/d/hdk/fortran.html
Dave
>
> Gerald
> ---
> htdocs/readings.html | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/htdocs/readings.html b/htdocs/readings.html
> index 0a978e8f..6e640af1 100644
> --- a/htdocs/readings.html
> +++ b/htdocs/readings.html
> @@ -463,11 +463,6 @@ names.
> Michel Olagnon's Fortran 90 List</a> contains a "Tests and
> Benchmarks" section mentioning commercial testsuites.
> </li>
> - <li>
> - <a
> href="http://www.personal.psu.edu/faculty/h/d/hdk/fortran.html">Herma
> n
> - D. Knoble's Fortran Resources</a> contain some sections on
> compiler
> - validation and benchmarking.
> - </li>
> <li>
> <cite>Complying with Fortran 90, How does the current crop
> of
> Fortran 90 compilers measure up to the standard?</cite>,
> Steven
prev parent reply other threads:[~2023-02-01 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 9:56 Gerald Pfeifer
2023-02-01 16:23 ` David Malcolm [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=a34e82bda9cbf265e4b90e9db0f8b553685fe714.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).