From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B58323858C78; Fri, 12 Apr 2024 08:59:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B58323858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712912368; bh=zuDI+R3gh2RWf0eOjuPDQ7dVxYI39M4tZbDWessjDmc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZSYhyMSyEJJqAHPP3qj1lI4dcBZjgrTG7ePjwRp+umT3nJG8cXjVHr+EVB6DksMKY mOs7RQuuGaTB44oCXWd/epmiSbCr0kvLar2HAcn9kW55WBpGn3jXEwWgq0o8LHB+it l+WWuDmAo290EQva/lMgY05BIdSmeRKWtZRLOtCY= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzEwMzQ5Nl0gW0YyMDE4XVtUUzI5MTEzXSBD?= =?UTF-8?B?X1NJWkVPRiDigJMgcmVqZWN0cyBub3cgdmFsaWQgYXJncyB3aXRoICdtdXN0?= =?UTF-8?B?IGJlIGFuIGludGVyb3BlcmFibGUgZGF0YSBlbnRpdHkn?= Date: Fri, 12 Apr 2024 08:59:27 +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.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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=3D103496 --- Comment #4 from Tobias Burnus --- (In reply to anlauf from comment #3) > The code in comment#0 compiles at r14-9893-gded646c91d2c0f > and gives the indicated results. which is the commit: Fortran: fix argument checking of intrinsics C_SIZEOF, C_F_POINTER [PR1065= 00] It looks as if the issue is fixed, but gfortran misses a tescast to check t= hat the obtained value is correct. c_sizeof_7.f90 contains tests, but I think there should be a run time trst = that the obtained values are correct; I think some are constants such that a tree-dump scan test would work as well, but for the dynamic ones, a run time test seems zo be easier than trying to capture the generated code...=