From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 881F03858D37; Tue, 19 Mar 2024 16:07:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 881F03858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710864462; bh=2jGr7Mh9N482e4OHUjS7xTi+e/x/xL5jbBD6rvAKJq4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ftMLMbiE2z5GUE4ZdmOj5wbvWDOdBk208InJPQxonbX7vbLvyIhrwVFydqjC2FnYi XTIdC5Vw4m87T5nzWY5qx88KP87bKCwWqgA92b7814S5O+jdFgbe/XHThJu3dFXl7H 1kIw/m2mrhKxQ4o+U8ClS1LoH4u4Vl9JX0iAmIEw= From: "ghlixo at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 11.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ghlixo at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106295 --- 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 tim= e, 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 sy= mbol 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.=