From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 02D5B385842B; Wed, 29 Mar 2023 19:42:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 02D5B385842B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680118929; bh=4OM60CxqL7nl+SymcPmHj8ENcCwiRVcRI7gUm9gFHpA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pYqTlaig58VrD549yFKb4MfKSgPr9nQaGvYvcnnJjPAqGo1bipLTuxYCtQc1iK17H ee5IjCnSni1si+eDF5KBkpPjy6DB11c3CiMduAEzV3U22g4Ts7a823YrzHBm2khobx 09cm+aa7Jqio7CV0FqtVYCy1562x0YA3fV79kxks= From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109322] -fc-prototypes does not correctly translate INTEGER(KIND=C_SIZE_T), and other sizes Date: Wed, 29 Mar 2023 19:42:08 +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: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 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=3D109322 --- Comment #3 from Steve Kargl -= -- On Wed, Mar 29, 2023 at 05:50:05PM +0000, emr-gnu at hev dot psu.edu wrote: >=20 >=20 > Extending my original demonstrator, if you add a "INTEGER(KIND=3DC_INT64_= T) :: > E", you get the following output: >=20 > > gfortran -m32 -fc-prototypes -fsyntax-only foo.f90 >=20 > long a; > {...} > long_long e; > } bar; The companion C processor is gcc. It is generating prototypes for that C processor. If one is manipulating the environment with a command line option such as -m32 or -m64, then one likely needs to use the same option=20 with gcc. Does 'gcc -m32' support "long_long"? If it doesn't, then you'll need to hack on=20 gcc/fortran/dump-parse-tree.cc gcc/fortran/iso-c-binding.def gcc/fortran/trans-types.cc=