From: Tobias Burnus <tobias@codesourcery.com>
To: Thomas Koenig <tkoenig@netcologne.de>,
Richard Biener <rguenther@suse.de>
Cc: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
Steve Kargl <sgk@troutmask.apl.washington.edu>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR37336 finalization
Date: Wed, 8 Mar 2023 11:28:51 +0100 [thread overview]
Message-ID: <a76952cc-5c71-9176-0f38-dbf50e6e0aa1@codesourcery.com> (raw)
In-Reply-To: <ef938db3-697b-75fe-ed78-f9d2210c7eff@netcologne.de>
On 08.03.23 09:55, Thomas Koenig via Fortran wrote:
> And now comes the problem - no Fortran maintanier has access to SPEC
> 2017, as far as I know. The curse of closed-source benchmarks...
We (as in Codesourcery) have access to the older SPEC Accel and the
newer SPEC HPC (but not to SPEC CPU – which SUSE has access to). In SPEC
HPC, I did not see any 'final ::'.
For code using finalization: In the popular non-free
electronic-structure code VASP (used to calculate molecules), I see a
single 'final::'.
A similar less popular program is Octopus,
https://gitlab.com/octopus-code/octopus That would be a real-world code
that uses 45 times 'final', 80 times 'type, extends(...)' and a thousand
times 'class(...)'. Thus, that could be a real-world testcase. (I have
not built it for a longer time.* It includes a regression-test suite.)
Tobias
(*) Octopus: I haven't build it for a longer time, but I think it should
build without too much trouble. That was the program the group
co-developed where I did my master thesis. / If you want to see what it
does: https://en.wikipedia.org/wiki/Octopus_(software) or
https://octopus-code.org/
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2023-03-08 10:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 13:45 Paul Richard Thomas
2023-03-07 14:58 ` Thomas Koenig
2023-03-07 17:15 ` Steve Kargl
2023-03-08 7:32 ` Paul Richard Thomas
2023-03-08 8:05 ` Thomas Koenig
2023-03-08 8:14 ` Richard Biener
2023-03-08 8:55 ` Thomas Koenig
2023-03-08 9:10 ` Richard Biener
2023-03-08 12:27 ` Paul Richard Thomas
2023-03-08 10:28 ` Tobias Burnus [this message]
2023-03-08 9:14 ` Paul Richard Thomas
2023-03-08 9:21 ` Richard Biener
2023-03-08 14:55 ` Paul Richard Thomas
2023-03-08 14:57 ` Richard Biener
2023-03-08 21:35 ` Thomas Koenig
2023-03-09 7:13 ` Thomas Koenig
2023-03-09 8:32 ` Richard Biener
2023-03-09 8:18 ` Richard Biener
2023-03-09 12:43 ` Paul Richard Thomas
2023-03-09 17:30 ` Thomas Koenig
2023-03-10 3:56 ` Jerry D
2023-03-10 16:49 ` Paul Richard Thomas
2023-03-15 7:29 ` Paul Richard Thomas
2023-03-15 7:37 ` Richard Biener
2023-03-16 7:20 ` Paul Richard Thomas
2023-03-09 15:05 ` Steve Kargl
2023-03-08 15:12 ` Steve Kargl
2023-03-08 15:29 ` Andrew Benson
2023-03-08 16:29 ` Tobias Burnus
2023-03-08 17:12 ` Paul Richard Thomas
2023-06-02 13:42 ` Paul Richard Thomas
2023-06-03 5:50 ` Thomas Koenig
2023-06-03 7:32 ` Steve Kargl
2023-06-03 13:16 ` Paul Richard Thomas
2023-06-03 19:10 ` Harald Anlauf
2023-06-03 19:22 ` Thomas Koenig
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=a76952cc-5c71-9176-0f38-dbf50e6e0aa1@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=rguenther@suse.de \
--cc=sgk@troutmask.apl.washington.edu \
--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).