From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2C83F3858C39; Thu, 14 Mar 2024 09:26:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2C83F3858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710408413; bh=J/xpCLTUR87WEFQATYHw8TvjoQ14u8somysbNeLnrgg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PqZykDHK6NkyzLlXP25nSsEethoz52lajTPFHyVoOoGTtjmGz5yW1Qla/5eb8VgGT KKVbHrtdMPoG3yx67eVshAi0sLsTBrn6cf0q7sCaS/hJTradJKMKpakkRXvp13WPn5 lPmlF+0DLTl7TBEioCk4dpfg0e6ROfqr8xEP/ITI= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBsaWJmb3J0cmFuLzExNDMwNF0gWzEzLzE0IFJlZ3Jlc3Np?= =?UTF-8?B?b25dIGxpYmdmb3J0cmFuIEkvTyDigJMgYm9ndXMgIlNlbWljb2xvbiBub3Qg?= =?UTF-8?B?YWxsb3dlZCBhcyBzZXBhcmF0b3Igd2l0aCBERUNJTUFMPSdwb2ludCci?= Date: Thu, 14 Mar 2024 09:26:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D114304 --- Comment #19 from Tobias Burnus --- Regarding the LAPACK issue: Actually, I am inclined to * regard it as LAPACK bug * that was also fixed upstream, see comment 6, to make g95 happy. as ';' is not a value separator - while ' ;' is fine, where the blank is a value separator. My testcase of comment 4 therefore always used a space before the ',' / ';'. * * * I have now created an extended testcase, attached to PR105473 as attachment 57695. (Only testing integer/real parsing, not reading the char afterward a= s in comment 4.) The same testcase can also be found at https://godbolt.org/z/14h48167W and shows the result with gfortran, ifort, ifx and flag. I used this result to = add comments to the testcases. * * * For some F2023 wording, see comment 14 above. And I have to admit that I am rather confused by the results as there does = not seem to be any consistent pattern; there are cases where I agree with gfortran's error even though neither ifort nor flang show one, while for others, I think gfortran gets it wrong. In particular, I think for the following cases: call t('point', ';') ! gfortran: no error, others: error =E2=86=92 IMHO invalid: not a value separator and not an integer. call t('point', '5;') ! gfortran: no error shown, others: error =E2=86=92 This is the LAPACK example but for integers. I think ';' is invalid as it is not part of the integer but also not a va= lue separator. call t('comma', '7 ,') ! gfortran: error; others: no error =E2=86=92 IMHO valid - I think the ' ' as value separator is sufficient. call t('point', '3.3,', .true.) ! gfortran/flag: error shown; ifort: no e= rror =E2=86=92 What's wrong with a comma as value separator? call t('comma', '3,3;', .true.) ! gfortran: error shown; others: no error =E2=86=92 Same, except that ';' is now the value separator But in the following cases, I think gfortran is *right*: call t('point', '5.') ! gfortran/flang: Error shown, ifort: no error =E2=86=92 '.' is not part of an integer nor a value separator call t('comma', '5,') ! gfortran: error; others: no error =E2=86=92 Likewise for ',' - the ',' is not part of an integer nor a value = separator Disclaimer: I might have easily overlooked some fine print.=