From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D5C163858CDA; Wed, 29 Mar 2023 21:24:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D5C163858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680125092; bh=3yff+f8Tp3nU+BhTVTpEHli9kqjiKOwFknENT/670Bo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wYD3HJF8GONd1hnIgtVu5yISHpzPBVc5OwiK8Vy+l2ABpLH/9ocqwtcb5TtykTKT8 rpYzbAg5VjfF3DXYc5WwbyFgTuu62CEiuK1S1YN+2lXX6aaCaIRJaZpnrH+5j2fV2h S6PlgACzRVrTxpeqtqor/gLUNCDCGkUbwnkDICAM= From: "pinskia at gcc dot gnu.org" 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 21:24: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: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org 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: bug_status cf_reconfirmed_on everconfirmed 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 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2023-03-29 Ever confirmed|0 |1 --- Comment #4 from Andrew Pinski --- (In reply to Eric Reischer from comment #2) > However, if you are, say, creating an > API that has autogenerated files redistributed (e.g., a base Fortran pack= age > and then autogenerated and distributed C/C++ header files), the types > generated using -fc-prototypes are not safely transportable to another > compiler with the requested variable sizes. Yes you should use this option this wayt; you can always post process the generated headers. For -m32 vs -m64, you could generate two headers and have a master header t= hat includes one or another. There is no way to store these headers in a repo unless you post process th= em.=