From 0115c3716781741505a86e8923b51c8aa101b89b Mon Sep 17 00:00:00 2001 From: "Ted M. Johnson" Date: Wed, 21 Jan 2026 20:43:22 -0700 Subject: [PATCH] [flang] Disable invalid PUBLIC/PRIVATE pre-F2018 test This patch disables a test which is the old access-spec functionality. A recent flang patch enforces PUBLIC and PRIVATE accessibility as defined starting in F2018, and passed initially as paper J3/13-327r3; the description is from "Whats New In Fortran 2018" by John Reid: If a module A uses module B, the default accessibility for entities it accesses from B is that of A. Specifying another accessibility for each entity is awkward and error prone. It is now possible for the name of a module to be included in the list of names of entities made public or private on a public or private statement. This sets the default for all entities accessed from that module. In the F2023 standard, this is clause 8.6.1(1). --- Fortran/gfortran/regression/DisabledFiles.cmake | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Fortran/gfortran/regression/DisabledFiles.cmake b/Fortran/gfortran/regression/DisabledFiles.cmake index 2deefffb8547..cae90e585ec2 100644 --- a/Fortran/gfortran/regression/DisabledFiles.cmake +++ b/Fortran/gfortran/regression/DisabledFiles.cmake @@ -156,6 +156,10 @@ file(GLOB UNSUPPORTED_FILES CONFIGURE_DEPENDS # Function call via a PROCEDURE() proc_ptr_comp_46.f90 + + # Fortran 2018 changed the way association works with modules and USE, + # making this test invalid now; flang supports it, gfortran does not. + public_private_module.f90 ) # These tests are skipped because they hit a 'not yet implemented' assertion