From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7676E3858C39; Fri, 14 Oct 2022 22:21:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7676E3858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665786060; bh=B92Fm7NPkMCf2W49EAHlwUE/Z3vjiaiUZITJv6OUzBc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ad1B1w/VfH0lL0C+Z5IkcG4ebNrKcxVxbWFh99EVzAHfZyIkWu8HhavwlETN9DAz4 YSfcomQQVTPBgnWzEsPr+oVO6I7QUlIl1H5oRLcXqjqY4l+W2odORp9Yy9oRHqI4AM ACl+sO5PlNcRpDr4QwwCl1kzqO1i88bkU66IGJqA= From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzEwNzI2Nl0gUmVqZWN0IGtpbmQ9NCBjaGFy?= =?UTF-8?B?YWN0ZXJzIGZvciBCSU5EKEMpIOKAkyBpdCBpbnZhbGlkIGFuZCBnZW5lcmF0?= =?UTF-8?B?ZXMgd3JvbmcgY29kZQ==?= Date: Fri, 14 Oct 2022 22:21:00 +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: 13.0 X-Bugzilla-Keywords: accepts-invalid, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 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=3D107266 --- Comment #6 from Steve Kargl -= -- On Fri, Oct 14, 2022 at 09:36:59PM +0000, burnus at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107266 >=20 > --- Comment #5 from Tobias Burnus --- > I do note that we already have bind(C) + kind=3D4 examples: > https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dblob;f=3Dgcc/testsuite/gfortran.= dg/PR100906.f90 > integer, parameter :: c_ucs4_char =3D 4 > and more. F2023 does not have an interoperable type of c_ucs4_char. F2023 has SELECTED_CHAR_KIND("ISO_10646"), which can be used as in the example code (see 22-007r1.pdf, 16.9.180): 14 SUBROUTINE create_date_string(string) 15 INTRINSIC date_and_time,selected_char_kind 16 INTEGER,PARAMETER :: ucs4 =3D selected_char_kind("ISO_10646") 17 CHARACTER(1,UCS4),PARAMETER :: nen=3DCHAR(INT(Z'5e74'),UCS4), & !year 18 gatsu=3DCHAR(INT(Z'6708'),UCS4), & !month 19 nichi=3DCHAR(INT(Z'65e5'),UCS4) !day 20 CHARACTER(len=3D *, kind=3D ucs4) string 21 INTEGER values(8) 22 CALL date_and_time(values=3Dvalues) 23 WRITE(string,1) values(1),nen,values(2),gatsu,values(3),nichi 24 1 FORMAT(I0,A,I0,A,I0,A) 25 END SUBROUTINE Neither UCS4, ISO_10646, ISO 10646, nor 10646 appear in=20 F2023 Section 18. On J3 Fortran github, there are no proposals/requests for interoperability with ISO 10646. > =3D> Keep permitting it but fix it I'll update my patch to use "gfc_notify_std (GFC_STD_GNU, ...)" as this is clearly an extension to the Fortran standard.=