From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4F4D53858CDA; Thu, 30 Mar 2023 20:10:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F4D53858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680207024; bh=oTS0ob6UAbC2G9o/GzljcdvBr4NlH7qHeYkdz53pC6M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PH9Uke75X/IKQim/PeFfcOksN0wk9Rw3+JVr3S17rfkkFVvQnZ7YmHEEVrj/j4XXq Suw8agC2WUQTf2pNE0bIWSqhfkikffkrCToXJp/hiY8mhx/lz6ZyAn6nX6b1azF435 7K9mXra/2iTQymwT/zkhuUHAPQd6crk5vtFlSkVU= 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: Thu, 30 Mar 2023 20:10:24 +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: WAITING 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 #11 from Steve Kargl = --- On Thu, Mar 30, 2023 at 07:21:21PM +0000, pinskia at gcc dot gnu.org wrote: >=20 > For ILP32 (32bit x86) and LLP64IL32 (64bit Windows/mingw) targets, it wil= l use > c_long_long which is outputted wrong. Anyways I fixed the bug with respec= t of > c_long_long being outputted incorrectly as long_long rather than "long lo= ng" > too. (r13-6940-ga7df3bea9cf1e4 and backported to GCC 12: > r12-9370-g429b75db39aa89 ). >=20 I quite agree that your patch fixed a problem. My comment was meant for the OP, who would like to "integer(c_int64_t) a" translated to "int64_t a;" That's isn't going to happen anytime soon. I left the PR open as an enhancement request. In 10 years, if I'm still around I close it.=