Re: [Patch, fortran] PR87477 - [meta-bug] [F03] issues concerning the ASSOCIATE statement

Thanks Mikael. Pushed as r14-1487-g3c2eba4b7a2355ed5099e35332388206c484744d I should have credited you with the comments that you made about the half baked patch, which pushed me to this patch. Regards Paul On Thu, 1 Jun 2023 at 18:58, Mikael Morin wrote: > Le 01/06/2023 à 17:20, Paul Richar

Re: [Patch, fortran] PR37336 finalization

Hi All, I propose to backport r13-6747-gd7caf313525a46f200d7f5db1ba893f853774aee to 12-branch very soon. Before that, I propose to remove the F2003/2008 finalization of structure and array constructors in 13- and 14-branches. I can see why it was removed from the standard in a correction to F2008

A doubt about IMPORT and SELECT TYPE

Hi, I have a doubt about IMPORT and SELECT TYPE, please see the forwarded message below (that also has a sample code), as well https://www.ibm.com/docs/en/xffbg/121.141?topic=attributes-import-fortran-2003 What is the correct way? Thanks. Regards. Jorge. - Forwarded message - From: "

Re: A doubt about IMPORT and SELECT TYPE

Hi Jorge, As I posted in the Intel Community, the error generated by gfortran (and nagfor) is consistent with the F2003 constraint: C1210 (R1209) The IMPORT statement is allowed only in an interface-body. Could you please raise a problem report in gcc Bugzilla? Thanks Paul On Fri, 2 Jun 2023 a

Re: A doubt about IMPORT and SELECT TYPE

Hi Jorge, PRs 108650/106035 cover this problem. Thanks Paul On Fri, 2 Jun 2023 at 15:04, Jorge D'Elia via Fortran wrote: > > Hi, > > I have a doubt about IMPORT and SELECT TYPE, please see the > forwarded message below (that also has a sample code), as well > > https://www.ibm.com/docs/en/xffb

Re: A doubt about IMPORT and SELECT TYPE

On Fri, Jun 02, 2023 at 03:53:44PM +0100, Paul Richard Thomas via Fortran wrote: > Hi Jorge, > > As I posted in the Intel Community, the error generated by gfortran > (and nagfor) is consistent with the F2003 constraint: C1210 (R1209) > The IMPORT statement is allowed only in an interface-body. >

[PATCH, committed] Fortran: fix diagnostics for SELECT RANK [PR100607]

Dear all, I've committed that attached simple patch on behalf of Steve after discussion in the PR and regtesting on x86_64-pc-linux-gnu. It fixes a duplicate error message and an ICE. Pushed as r14-1505-gfae09dfc0e6bf4cfe35d817558827aea78c6426f . Thanks, Harald From fae09dfc0e6bf4cfe35d8175588

Re: A doubt about IMPORT and SELECT TYPE

Hi Steve, As noted in the previous email :-), although I didn't mention the partially cooked patch. One day, once F2003 is sorted, I might turn to F2008/18! Cheers Paul On Fri, 2 Jun 2023, 16:27 Steve Kargl via Fortran, wrote: > On Fri, Jun 02, 2023 at 03:53:44PM +0100, Paul Richard Thomas

Re: A doubt about IMPORT and SELECT TYPE

Oh, I'm not asking you or any of the other regular contributors to gfortran to pick up my WIP patch and finish the last 5%. Now, lurkers on the mailing list, who have always wanted to give back, well I'm more than willing to help explain the patch and what I think needs to be done if they are so i

Re: [PATCH, committed] Fortran: fix diagnostics for SELECT RANK [PR100607]

Hi Harald, It looks good to me. Thanks to you and Steve for the fix. I suggest that it is such and obvious one that it deserved back-porting. Cheers Paul On Fri, 2 Jun 2023 at 19:06, Harald Anlauf via Fortran wrote: > > Dear all, > > I've committed that attached simple patch on behalf of Steve

Re: [Patch, fortran] PR37336 finalization

Hi Paul, I propose to backport r13-6747-gd7caf313525a46f200d7f5db1ba893f853774aee to 12-branch very soon. Is this something that we usually do? While finalization was basically broken before, some people still used working subsets (or subsets that were broken, and they adapted or wrote their