Re: [Fortran, Patch, PR119349, v1] Fix regression of polymorphic dummy sourced from array constructors.

Am 21.03.25 um 15:34 schrieb Paul Richard Thomas: I am reasonably familiar with the mess that is gfc_conv_procedure_call :-) It's only 2141 lines in a single function and eight levels of conditions / loops! I do not see what could possibly go wrong :-) Best regards Thomas

[PATCH] testsuite: Replace the cray_pointers_2.f90 no cycling hack with dg-skip-if

On Thu, Mar 27, 2025 at 06:11:25PM +, Sam James wrote: > >> diff --git a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90 > >> b/gcc/testsuite/gfortran.dg/cray_pointers_2.f90 > >> index 4351874825ed..a7e15bad850a 100644 > >> --- a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90 > >> +++ b/gcc/tests

GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs

My doubt : 1.Does the compilation option only need to support fortran versions above 9, o5r does it also need to support fortran 77? 2.Regarding parameter checking, *my idea is that after the user creates an array of a specified size, it is passed into the function as a parameter*. However, the arr

Re: [Fortran, Patch, PR119349, v1] Fix regression of polymorphic dummy sourced from array constructors.

Hi Andre, I am reasonably familiar with the mess that is gfc_conv_procedure_call :-) So in spite of you having a hard time explaining things today, I see your patch as verging on 'obvious' and is certainly the best that can be done without refactoring the whole thing. OK fo mainline. Thanks for

Re: GSoC Fortran – 2018/202x – Inquiry About Project Scope

On Thu, Mar 27, 2025 at 03:43:49PM +, Yuao Ma wrote: > > Thanks for sharing more details. I’ve realized that implementing half-cycle > trig functions can be quite tricky. If I get the chance to refine the patch, > I’d like to go through each function one by one (if the reviewers don’t mind), >

GSoC Draft Proposal Submission: Fortran 2018/202x

Hi GCC developers, I'm sharing the draft proposal for my GSoC project titled "Fortran 2018/202x". It has already been posted on the Fortran mailing list, where I received valuable feedback from gfortran developers. As mentioned on the GCC GSoC page, proposals should also be shared on the GCC mail

GSoC 2025 - Draft Proposal for Fortran 2018/202x - RFC

Dear gfortran developers, I have uploaded a draft proposal for the 'Fortran – 2018/202x' project to the platform. You can also find a PDF version at this Google Drive link: https://drive.google.com/file/d/1cSRPuWpXWHMwHdNItQluEYspLfylqZcU. Could you please review the proposal and provide feedback