Re: [Patch, fortran] PR117434 - [F08] gfortran rejects actual argument corresponding to procedure pointer dummy argument

2024-11-05 Thread Paul Richard Thomas
Hi Harald, Yes indeed about proc_ptr_56.f90 :-( That was a slip that occurred in the preparation of the patch for the list. I will indeed make proc_ptr_54.f90 compile-only for the time being. The latter was not elided from my platform for any level of optimization for the simple reason that system

[pushed: r15-4969] fortran: dynamically allocate error_buffer [PR117442]

2024-11-05 Thread David Malcolm
PR fortran/117442 reports a crash on exit of f951 when configured with --enable-gather-detailed-mem-stats. The crash happens if any diagnostics were ever buffered into error_buffer. The root cause is that error_buffer is statically allocated and thus has a non-trivial destructor called at exit. I

Re: [Patch, fortran] PR117434 - [F08] gfortran rejects actual argument corresponding to procedure pointer dummy argument

2024-11-05 Thread Iain Sandoe
Hi Folks. > On 5 Nov 2024, at 19:23, Harald Anlauf wrote: > > Hi Paul, > > Am 05.11.24 um 16:24 schrieb Paul Richard Thomas: >> Hi All, >> >> There is not much to say about the attached patch other than it is minimal >> :-) The testcases are probably a bit more than is strictly needed since th

Re: [Patch, fortran] PR117434 - [F08] gfortran rejects actual argument corresponding to procedure pointer dummy argument

2024-11-05 Thread Harald Anlauf
Hi Paul, Am 05.11.24 um 16:24 schrieb Paul Richard Thomas: Hi All, There is not much to say about the attached patch other than it is minimal :-) The testcases are probably a bit more than is strictly needed since the interface tests (proc_ptr_55.f90) are already tested elsewhere. However, it i

[Patch, fortran] PR117434 - [F08] gfortran rejects actual argument corresponding to procedure pointer dummy argument

2024-11-05 Thread Paul Richard Thomas
Hi All, There is not much to say about the attached patch other than it is minimal :-) The testcases are probably a bit more than is strictly needed since the interface tests (proc_ptr_55.f90) are already tested elsewhere. However, it is as well to check in this context. OK for mainline and 14-br