From: Kay Diederichs <kay.diederichs@uni-konstanz.de>
To: Arjen Markus <arjen.markus895@gmail.com>,
Andre Vehreschild <vehre@gmx.de>
Cc: Fortran List <fortran@gcc.gnu.org>
Subject: Re: is there a way to find out gfortran version and/or options from a given binary?
Date: Wed, 1 Jun 2022 12:16:33 +0200 [thread overview]
Message-ID: <d2053669-8d2d-117b-b766-e003f404a12f@uni-konstanz.de> (raw)
In-Reply-To: <CAMCbSMq1E2zWPrrcg7HUN_QL_AJ=0surwxsNL5G35jJbBQM8Hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
I tried your suggestion below, but it does not store the options unless
the -g option is used.
If -g is used, the executable _always_ has version and option info (no
extra code invoking compiler_version() and compiler_options() is
needed). Just use strings <binary> | grep GNU .
If -g is not used, no option info is in the executable.
Best wishes,
Kay
On 01.06.22 12:00, Arjen Markus wrote:
> staticv.f90 --
> ! Static information about the compiler? Not via parameters
> !
> program staticv
> use iso_fortran_env
>
> implicit none
> character(len=200) :: c, d
>
> c = compiler_version()
> d = compiler_options()
> write(*,*) c(1:1), d(1:)1
> end program staticv
>
--
Kay Diederichs http://strucbio.biologie.uni-konstanz.de
email: Kay.Diederichs@uni-konstanz.de Tel +49 7531 88 4049
Fachbereich Biologie, Universität Konstanz, Box M647, D-78457 Konstanz
This e-mail is digitally signed. If your e-mail client does not have the
necessary capabilities, just ignore the attached signature "smime.p7s".
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5322 bytes --]
next prev parent reply other threads:[~2022-06-01 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:42 Kay Diederichs
2022-06-01 9:30 ` Arjen Markus
2022-06-01 9:41 ` Kay Diederichs
2022-06-01 9:50 ` Andre Vehreschild
2022-06-01 9:53 ` Arjen Markus
2022-06-01 10:00 ` Arjen Markus
2022-06-01 10:16 ` Kay Diederichs [this message]
2022-06-01 11:36 ` Arjen Markus
2022-06-01 11:46 ` Arjen Markus
2022-06-01 12:04 ` Kay Diederichs
2022-06-01 12:19 ` Arjen Markus
2022-06-02 19:06 ` Janne Blomqvist
2022-06-02 19:33 ` Kay Diederichs
2022-06-03 5:22 ` Janne Blomqvist
2022-06-03 6:47 ` Arjen Markus
[not found] ` <14d31069-82ab-5a7a-2f35-15411da30141@uni-konstanz.de>
2022-06-03 7:30 ` Arjen Markus
2022-06-03 8:16 ` Janne Blomqvist
2022-06-03 10:12 ` Kay Diederichs
2022-06-03 10:12 ` Kay Diederichs
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=d2053669-8d2d-117b-b766-e003f404a12f@uni-konstanz.de \
--to=kay.diederichs@uni-konstanz.de \
--cc=arjen.markus895@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=vehre@gmx.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).