[committed] testsuite/gfortran.dg/open_errors_2.f90: Remove now-redundant file deletion

2024-09-26 Thread Hans-Peter Nilsson
Only because I wrote earlier that I'd do this patch. Committed as obvious. Sanity-checked by running the test in a native tree as "make check-gcc-fortran RUNTESTFLAGS=dg.exp=open_errors_2.f90" -- >8 -- Now that fort.N files are removed by the testsuite framework, remove this single "manual" file

Re: Fwd: [patch, fortran] Matmul and dot_product for unsigned

2024-09-26 Thread rep . dot . nop
. > >I have also committed, right now, a fix for the failure of >unsigned_25.f90 on 32-bit systems as obvious. could we maybe walk all sizes, if they fit, according to the preprocessor? > >Best regards >

Fwd: [patch, fortran] Matmul and dot_product for unsigned

2024-09-26 Thread Thomas Koenig
[I just saw I hit the wrong reply button on this] Hi Andre, thanks for your answers. I am ok with the patch. I have committed all four patches. Thanks a lot for the reviews! Now for the remaining intrinsics (FINDLOC, MAXLOC, MINLOC, MAXVAL, MINVAL, CSHIFT and EOSHIFT still missing). And af

Re: [PATCH] gfortran testsuite: Remove unit-files in files having open-statements, PR116701

2024-09-26 Thread rep . dot . nop
On 25 September 2024 22:08:15 CEST, rep.dot@gmail.com wrote: > >>Your interpretation of my typo is correct. Along with Andre I like auto >>cleanup. On new test cases we try to have them self delete whether they pass >>or fail. >> > >so why don't we issue the cleanup then, regardless?

[PATCH] doc: Remove variables from fortran options in index

2024-09-26 Thread Mikael Morin
From: Mikael Morin With this change, -ffixed-line-length-n and -ffree-line-length-n are the only remaining options with variables appearing in the index. But I think they are better left as-is. I refrained from adding the missing syntactic variant in the documentation of options allowing both s

[COMMITTED] testsuite: XFAIL gfortran.dg/initialization_25.f90 properly

2024-09-26 Thread Sam James
The test was disabled/XFAIL'd informally in r0-100012-gcdc6637d7c78ec, but r15-3890-g34bf6aa41ba539 didn't realize this, causing a FAIL. Fix that by marking it as XFAIL per the original intent. gcc/testsuite/ChangeLog: PR fortran/35779 PR fortran/116858 * gfortran.dg/init

[Fortran, Patch, PR93158, v1] Fix ICE with coarrays on submodules

2024-09-26 Thread Andre Vehreschild
Hi all, attached patch fixes an ICE when a derived type was used as a coarray in a submodule. The fix is to not allow caf-token creation for vtypes. Again this, like the previous patch on pr80235, feels like fixing the symptom and not the cause. But I can't find where it goes wrong. So if some one

[pushed] doc: Remove index reference to removed documentation in, fortran manual

2024-09-26 Thread Mikael Morin
Checked with make html pdf. Pushed.From e9f341426567442a70747f89b6b954a005ca287a Mon Sep 17 00:00:00 2001 From: Mikael Morin Date: Thu, 26 Sep 2024 14:23:06 +0200 Subject: [PATCH] doc: Remove index reference to removed documentation in fortran manual Fortran option -M used to be an alias for -J

[COMMITTED 2/2] testsuite: fix hyphen typos

2024-09-26 Thread Sam James
gcc/testsuite/ChangeLog: * g++.dg/modules/reparent-1_c.C: Fix whitespace around '-' in dg directive. * gfortran.dg/initialization_25.f90: Ditto. --- Committed as obvious. gcc/testsuite/g++.dg/modules/reparent-1_c.C | 2 +- gcc/testsuite/gfortran.dg/initialization_25.f90 | 4

[COMMITTED 1/2] testsuite: fix comment-only directive typos

2024-09-26 Thread Sam James
Doing this to avoid FPs from grepping but also to avoid the potential for people learning bad habits. gcc/testsuite/ChangeLog: * gfortran.dg/coarray/caf.exp: Fix 'dg-do-run' typo. * lib/gfortran-dg.exp: Ditto. * lib/gm2-dg.exp: Ditto. * lib/go-dg.exp: Ditto. --- Co