From: Arjen Markus <arjen.markus895@gmail.com>
To: Kay Diederichs <kay.diederichs@uni-konstanz.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 11:30:52 +0200 [thread overview]
Message-ID: <CAMCbSMoMdd=_b-JV9EbJmy+wgGtmY-g6s_eJ5ZbaK8DGvp7KqQ@mail.gmail.com> (raw)
In-Reply-To: <t778ph$8oo$1@ciao.gmane.io>
Are you perhaps looking for the compiler_version() and compiler_options()
functions? I use them like this, they were defined in Fortran 2008 if I am
not mistaken:
WRITE( lurep, '(a)' ) 'Report of simulation'
WRITE( lurep, '(a)' ) '--------------------'
WRITE( lurep, '(a)' ) 'Compiler version: ',
compiler_version()
WRITE( lurep, '(a)' ) 'Compiler options: ',
compiler_options()
Regards,
Arjen
Op wo 1 jun. 2022 om 10:42 schreef Kay Diederichs <
kay.diederichs@uni-konstanz.de>:
> Hi,
>
> is there any gfortran option and/or version information available from/in
> a binary? Maybe accessible with objdump or strings?
>
> For ifort, we use the -sox option ("This option tells the compiler to save
> the compilation options and version number in the executable file. ...").
> This enables e.g.
> strings /path/to/binary | grep Intel
>
> Or is there a gfortran option that makes this accessible in a binary?
>
> Thanks,
> Kay
>
>
>
next prev parent reply other threads:[~2022-06-01 9:31 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 [this message]
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
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='CAMCbSMoMdd=_b-JV9EbJmy+wgGtmY-g6s_eJ5ZbaK8DGvp7KqQ@mail.gmail.com' \
--to=arjen.markus895@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=kay.diederichs@uni-konstanz.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).