From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C4B9D3857008; Wed, 10 May 2023 18:55:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4B9D3857008
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683744928;
	bh=YKosr4ktTWmusFyv9WyOLFcZ7fhiwKOZ6t/ymusoFQ0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=iRsdA97PFx80O6tfww4CkjtC4u9StZ8LlJlb83PMQOw/1XR1hSn8qOLm62p7LBi71
	 rZbJ/qhCfSzt3Xtu3G3BQl6i5ZmlhNFRqBAoBqqx2VgUZQm1Htz3tt6QHTM1rRzDJ+
	 IE5mKh9uahfhGwPD2g/QxqYSW7MhGXzlmLx50bco=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109788] [14 Regression] gcc/hwint.h:293:61: runtime
 error: shift exponent 64 is too large for 64-bit type 'long unsigned int
 since r14-377-gc92b8be9b52b7e
Date: Wed, 10 May 2023 18:55:28 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109788-4-0UPtY3Df1Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109788-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Of course, if libgfortran plans to bump soname for GCC 14, that would be ok,
but not ok otherwise (you could e.g. keep the old symbol as is and add a
differently named entrypoint that used the new prototype).
But, as I wrote, the size_t vs. integer(kind=3D4) difference isn't the only
problem, the other is that the FUNCTION_TYPE created in the FE for the func=
tion
has just 5 arguments instead of 6 for some reason.=