250924.093452.CST MATLAB R2025b still has the bug regarding internal subroutines; update compile.m accordingly

Author: zaikunzhang

matlab/setup_tools/compile.m

@@ -92,7 +92,7 @@ function compile(solvers, mexdir, fortd, gateways, options)
     % -ftrampoline-impl=heap instructs the compiler to put the trampolines on the heap instead of the
     % stack. This option is available since gcc/gfortran 14. Without this option, executable stacks
     % will be generated by the internal subroutines passed as actual arguments. This is related to
-    % a bug of MATLAB R2025a on Linux, which segfaults when handling Fortran MEX files with internal
+    % a bug of MATLAB R2025a/b on Linux, which segfaults when handling Fortran MEX files with internal
     % procedures. For details, see the `support_internal_procedures` part below and
     % https://fortran-lang.discourse.group/t/implementation-of-a-parametrized-objective-function-without-using-module-variables-or-internal-subroutines/9919?u=zaikunzhang
     % First, get the major version of GCC corresponding to the libgcc used by the Fortran MEX.
@@ -153,7 +153,7 @@ function compile(solvers, mexdir, fortd, gateways, options)
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 % Zaikun 20250720:
-% The following code is to circumvent a bug in MATLAB R2025a, which segfaults on Linux when the
+% The following code is to circumvent a bug in MATLAB R2025a/b, which segfaults on Linux when the
 % Fortran files contain internal procedures that are passed as actual arguments to other procedures,
 % provided that the Fortran compiler is gfortran and the option -ftrampoline-impl=heap is not used.
 % To avoid this bug, we replace gateways/*_mex.F90 with gateways/R2025a/*_mex.F90, and
@@ -165,13 +165,13 @@ function compile(solvers, mexdir, fortd, gateways, options)
 % https://stackoverflow.com/questions/79699706/matlab-2025a-vs-fortran-mex-files-with-internal-subroutines
 % https://fortran-lang.discourse.group/t/implementation-of-a-parametrized-objective-function-without-using-module-variables-or-internal-subroutines
 % https://stackoverflow.com/questions/79705107/fortran-implementating-a-parametrized-objective-function-without-using-module-v
-matlab_supports_ip = (isMATLABReleaseOlderThan('R2025a')  || ~isMATLABReleaseOlderThan('R2025b'));
+matlab_supports_ip = (isMATLABReleaseOlderThan('R2025a')  || ~isMATLABReleaseOlderThan('R2026a'));
 compiler_supports_ip = (~contains(compiler_manufacturer, 'gnu') || contains(compiler_options, '-ftrampoline-impl=heap'));
 support_internal_procedures = (matlab_supports_ip || compiler_supports_ip);
 if ~support_internal_procedures
     if verbose
         warning('prima:ThreadRecursionUnsafe', ...
-            ['MATLAB R2025a has a bug that causes segmentation faults when handling Fortran MEX files with internal procedures.\n', ...
+            ['MATLAB R2025a/b has a bug that causes segmentation faults when handling Fortran MEX files with internal procedures.\n', ...
             '         PRIMA is adapted to circumvent this bug but it becomes thread-unsafe and recursion-unsafe.']);
     end
     % Replace the files. N.B.: The .*90 files have become .* after the code refactoring in setup.m.