From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CC9D3385771A; Wed, 10 May 2023 18:47:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC9D3385771A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683744473; bh=62XNtCKy/U8Uf4pSIqwrGydenEIrmgPN36+Zdf1t7jI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Yp3+Kh+eBDmKPXm8/yY2RmYvIc/6QJJOcGk6J6coHp7zJ6me/b43JTyDCR7WQdM3N c3TpygyA9jULob4lgU/G1O08R9XnDb3qwANbfZolcZDDVIoNJI887YW0V6yYxn7MNt /EVqxHQeCK5ZrmOMowfZ6CsViKH7ld5PrC/ZUA+8= From: "anlauf at gcc dot 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:47:52 +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: anlauf 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: cc attachments.created 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=3D109788 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #7 from anlauf at gcc dot gnu.org --- Created attachment 55040 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D55040&action=3Dedit libgfortran patch It appears that the prototypes of the character variants of the SPREAD intrinsic were not updated at the time when the character length type was changed from int to size_t. Does the attached patch fix your observation?=