Re: F2018 C937

2021-08-23 Thread Arjen Markus via Fortran
Hi Steve, yes, the extra macro did the job, so the testuite has run. So, this means the patch has to be adapted. I will report the unexpectedly failing tests in a separate mail. Regards, Arjen Op ma 23 aug. 2021 om 19:18 schreef Steve Kargl < s...@troutmask.apl.washington.edu>: > Hi Arjen, >

Re: F2018 C937

2021-08-23 Thread Steve Kargl via Fortran
Hi Arjen, Don't know if you've made any progress with cygwin (yes, I saw the other thread). I lurk on the J3 Fortran mailing list, and have come to learn that C937 has been deleted in the draft for Fortran 202x. What this means is that the "gcc_error ()" statement will need to be changed to use

Re: F2018 C937

2021-08-20 Thread Arjen Markus via Fortran
Yes, I already had arranged for that copyright one and a half years ago, but my first attempts failed (learning curve, real life getting in the way etc.) Op vr 20 aug. 2021 om 08:47 schreef Steve Kargl < s...@troutmask.apl.washington.edu>: > Feel free to ask questions. I forgot to point to >

Re: F2018 C937

2021-08-20 Thread Steve Kargl via Fortran
Feel free to ask questions. I forgot to point to the contributing page https://gcc.gnu.org/contribute.html At one time, you need to assign copyright to the FSF. That is no longer required. Scan the above page for details. -- steve On Fri, Aug 20, 2021 at 08:36:42AM +0200, Arjen Markus

Re: F2018 C937

2021-08-20 Thread Arjen Markus via Fortran
Hi Steve, thanks for this detailed workflow. I am familiar enough with git to know that there are myriads of procedures possible ;). Like you said, the first three steps have been done. I will get working on step 4 and work my way down the list. Regards, Arjen Op do 19 aug. 2021 om 18:23

Re: F2018 C937

2021-08-19 Thread Steve Kargl via Fortran
Arjen, If this is your first go around with patching gfortran, I'll suggest running the testsuite (if you haven't, see step 5. below; if you have see step 6.). I suspect you already know much of what I enumerate below, but it may help others. With a bug report, the workflow for me is/was 1.

Re: F2018 C937

2021-08-19 Thread Arjen Markus via Fortran
I have applied the patches locally (take care to restore the tabs ;)). Should I now commit these changes or is there a more formal procedure involved? Regards, Arjen Op do 19 aug. 2021 om 08:59 schreef Arjen Markus : > Hi Steve, > > I am willing to take up this challenge ;), as well as the

Re: F2018 C937

2021-08-19 Thread Arjen Markus via Fortran
Hi Steve, I am willing to take up this challenge ;), as well as the patch for C949. It would be my next attempt to get acquainted with the source code (a first step hopefully to actively contribute). Regards, Arjen Op di 17 aug. 2021 om 21:02 schreef Steve Kargl via Fortran <

F2018 C937

2021-08-17 Thread Steve Kargl via Fortran
For those that might care, I draw your attention to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101951 Good opportunity for a lurker to step forward and become a gfortran committer. Otherwise, this patch will fester in bugzilla the dozen or so other patches I've attached to PRs. -- Steve