Re: Possible funding of gfortran work

2023-06-01 Thread Jerry D via Fortran
On 6/1/23 2:18 AM, Andre Vehreschild wrote: Hi Damian, all, thank you for your input. I have incorporated most of it. Due to Germany stepping out of nuclear use, I have reduced the cites on these to a minimum. I don't know anything about the people evaluating the proposal and don't want to be re

Re: [PATCH] Fortran: force error on bad KIND specifier [PR88552]

2023-06-01 Thread Harald Anlauf via Fortran
Hi Mikael, Am 01.06.23 um 22:33 schrieb Mikael Morin: Hello, Le 01/06/2023 à 21:05, Harald Anlauf via Fortran a écrit : Dear all, we sometimes silently accept wrong declarations with unbalanced parentheses, as the PR and testcases therein show. It appears that the fix is obvious: use the exi

Re: [PATCH] Fortran: force error on bad KIND specifier [PR88552]

2023-06-01 Thread Mikael Morin
Hello, Le 01/06/2023 à 21:05, Harald Anlauf via Fortran a écrit : Dear all, we sometimes silently accept wrong declarations with unbalanced parentheses, as the PR and testcases therein show. It appears that the fix is obvious: use the existing error paths in gfc_match_kind_spec and error retur

[PATCH] Fortran: force error on bad KIND specifier [PR88552]

2023-06-01 Thread Harald Anlauf via Fortran
Dear all, we sometimes silently accept wrong declarations with unbalanced parentheses, as the PR and testcases therein show. It appears that the fix is obvious: use the existing error paths in gfc_match_kind_spec and error return from gfc_match_decl_type_spec. I'm still posting it here in case I

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

2023-06-01 Thread Mikael Morin
Le 01/06/2023 à 17:20, Paul Richard Thomas via Fortran a écrit : Hi All, This started out as the search for a fix to pr109948 and evolved to roll in 5 other prs. Basically parse_associate was far too clunky and, in anycase, existing functions in resolve.cc were well capable of doing the determi

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

2023-06-01 Thread Paul Richard Thomas via Fortran
Hi All, This started out as the search for a fix to pr109948 and evolved to roll in 5 other prs. Basically parse_associate was far too clunky and, in anycase, existing functions in resolve.cc were well capable of doing the determination of the target expression rank. While I was checking the comm

Re: Possible funding of gfortran work

2023-06-01 Thread Benson Muite via Fortran
On 6/1/23 12:18, Andre Vehreschild wrote: > Hi Damian, all, > > thank you for your input. I have incorporated most of it. Due to Germany > stepping out of nuclear use, I have reduced the cites on these to a minimum. I > don't know anything about the people evaluating the proposal and don't want to

Re: Possible funding of gfortran work

2023-06-01 Thread Mikael Morin
Hello, some more comments below: Le 01/06/2023 à 11:18, Andre Vehreschild a écrit : Hi Damian, all, thank you for your input. I have incorporated most of it. Due to Germany stepping out of nuclear use, I have reduced the cites on these to a minimum. I don't know anything about the people evalu

Re: Possible funding of gfortran work

2023-06-01 Thread Bernhard Reutner-Fischer via Fortran
On 1 June 2023 11:18:08 CEST, Andre Vehreschild via Fortran wrote: >Hi Damian, all, > >thank you for your input. I have incorporated most of it. Due to Germany >stepping out of nuclear use, I have reduced the cites on these to a minimum. I >don't know anything about the people evaluating the prop

Re: Possible funding of gfortran work

2023-06-01 Thread Andre Vehreschild via Fortran
Hi Damian, all, thank you for your input. I have incorporated most of it. Due to Germany stepping out of nuclear use, I have reduced the cites on these to a minimum. I don't know anything about the people evaluating the proposal and don't want to be rejected just because of ideological reasons. He