public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghlixo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/106295] INQUIRE statement bus error at runtime
Date: Tue, 19 Mar 2024 16:07:41 +0000	[thread overview]
Message-ID: <bug-106295-4-DeDDmAfBo8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106295-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106295

--- Comment #6 from ghlixo at gmail dot com ---
One last comment about this issue.

I maintain and distribute a Fortran subroutine package to users.  In my
experience, most of them are unaware that Fortran compilers evolve over time,
and that the compiler used to build the subroutine package might not be the
same version that they have installed.

It seems that simple form of link-time version control might alert them to the
problem, and avoid spurious problem reports.  Would not a reference to a symbol
in the run-time library dropped into compiled code when a library routine is
used solve the problem?  If the symbol definition changes when the library
changes, then it would be impossible to link old code with an incompatible
run-time library.

  parent reply	other threads:[~2024-03-19 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 13:09 [Bug libfortran/106295] New: " ghlixo at gmail dot com
2022-07-14 13:11 ` [Bug libfortran/106295] " ghlixo at gmail dot com
2022-07-14 13:12 ` ghlixo at gmail dot com
2022-07-14 13:13 ` ghlixo at gmail dot com
2022-07-14 18:37 ` anlauf at gcc dot gnu.org
2024-03-06  2:49 ` jvdelisle at gcc dot gnu.org
2024-03-19 16:07 ` ghlixo at gmail dot com [this message]
2024-03-19 17:22 ` jvdelisle at gcc dot gnu.org

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=bug-106295-4-DeDDmAfBo8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).