From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Kay Diederichs <kay.diederichs@uni-konstanz.de>
Cc: Arjen Markus <arjen.markus895@gmail.com>,
Andre Vehreschild <vehre@gmx.de>,
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: Thu, 2 Jun 2022 22:06:48 +0300 [thread overview]
Message-ID: <CAO9iq9HkNV8ZkAyLVwK-fq4O0MptP33WBweuZD=TEXu_+97oQQ@mail.gmail.com> (raw)
In-Reply-To: <d2053669-8d2d-117b-b766-e003f404a12f@uni-konstanz.de>
On Wed, Jun 1, 2022 at 1:16 PM Kay Diederichs
<kay.diederichs@uni-konstanz.de> wrote:
> If -g is used, the executable _always_ has version and option info
Well, isn't that the answer to your question then?
As an alternative approach, make a command-line option (say, "-v")
that prints the version number of the program, name of the author and
other pertinent information, as well as the output of
compiler_version() and compiler_options(), and then exits. That would
ensure that those calls won't be optimized away.
--
Janne Blomqvist
next prev parent reply other threads:[~2022-06-02 19:06 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
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 [this message]
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='CAO9iq9HkNV8ZkAyLVwK-fq4O0MptP33WBweuZD=TEXu_+97oQQ@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--cc=arjen.markus895@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=kay.diederichs@uni-konstanz.de \
--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).