diff options
author | Thomas Koenig <tkoenig@gcc.gnu.org> | 2025-05-06 18:05:41 +0200 |
---|---|---|
committer | Thomas Koenig <tkoenig@gcc.gnu.org> | 2025-05-06 18:07:06 +0200 |
commit | e7a2b8b76ae0c8f1e49c780aa82ebb5f0325f515 (patch) | |
tree | 5d23930741fa16f8e8620cf8c2bc325496c766ad /libstdc++-v3/include/std/numeric | |
parent | 76c882e341cb330a4e9f677a8c3541d573820255 (diff) | |
download | gcc-e7a2b8b76ae0c8f1e49c780aa82ebb5f0325f515.zip gcc-e7a2b8b76ae0c8f1e49c780aa82ebb5f0325f515.tar.gz gcc-e7a2b8b76ae0c8f1e49c780aa82ebb5f0325f515.tar.bz2 |
Fix PR 119928, formal arguments used to wrongly inferred for CLASS.
The problem was indeed that generating a formal from an actual
arglist is a bad idea when classes are involved. Fixed in the
attached patch. I think it still makes sense to remove the checks
when the other attributes are present (or PR96073 may come back
in different guise, even if I have to test case at present).
I have also converted the test to a run-time check.
gcc/fortran/ChangeLog:
PR fortran/119928
* interface.cc (gfc_check_dummy_characteristics): Do not issue
error if one dummy symbol has been generated from an actual
argument and the other one has OPTIONAL, INTENT, ALLOCATABLE,
POINTER, TARGET, VALUE, ASYNCHRONOUS or CONTIGUOUS.
(gfc_get_formal_from_actual_arglist): Do nothing if symbol
is a class.
gcc/testsuite/ChangeLog:
PR fortran/119928
* gfortran.dg/interface_60.f90: New test.
Diffstat (limited to 'libstdc++-v3/include/std/numeric')
0 files changed, 0 insertions, 0 deletions