From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by sourceware.org (Postfix) with ESMTPS id 8CDE03858C1F for ; Wed, 14 Jun 2023 08:28:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8CDE03858C1F Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmx.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1686731298; x=1687336098; i=vehre@gmx.de; bh=NBiPIw9VbQsLAXxan6Uaup5MY4rxNLC5PHbBkaz7mp4=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References; b=jv+E8Wf/rfjQeZuCmE1TyzTRgTChfzAxgMQV+jBqNbh7qjOLStfS7R/9GUmq6bpdNGYiekM V/XPg1+H5SYo4FcBEcXQhMe6XyGcMCMPrS2jNJ4U2PXEok2s24JXtW2wapJcUceRdUj+otETk cUHCmFzYvdiHkc3Ago0yeTm3s4zWhsKx5KHRCwQ1O8I/6yPkeETvK3wZCT8tpL784SiRNDXWO 8ZNVD+t/Il7eqQ+ZGs3gGCYUelVhKIbYpJNtYYj2TzjCJ2OVeQaw23htt2u6I7ssvBc2s7ZbP ERx2rOr/5fVXezlJk9sBYhppuS8IngZo1haqigjA2IXbe1mvClLQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from vepi2 ([80.141.190.195]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MBm1e-1qH0pS0b2S-00C8vs; Wed, 14 Jun 2023 10:28:18 +0200 Date: Wed, 14 Jun 2023 10:28:12 +0200 From: Andre Vehreschild To: Mikael Morin Cc: Damian Rouson , Thomas Koenig , Benson Muite , Jerry D , Paul Richard Thomas , GCC-Fortran-ML , Lexi Pimenidis , Nicolas =?UTF-8?B?S8O2bmln?= Subject: Re: Possible funding of gfortran work Message-ID: <20230614102812.593b558d@vepi2> In-Reply-To: <74690341-bde3-47f2-8750-26a05578668d@orange.fr> References: <4697f7be-ac3e-8c5d-f27c-3aec89b5b03f@protonmail.com> <0d923990-0b7a-a1ea-8389-bf3837e73ed0@gmail.com> <737bbf36-04a8-c1e4-b3aa-31121df66013@netcologne.de> <20230527132414.50184389@vepi2> <105c761a-5030-aee5-6587-2783a794f469@gmail.com> <20230530153242.54728d4d@vepi2> <2fa3240f-fbb8-23b6-2a10-24f9a415f729@netcologne.de> <5bde7c1f-3524-7f2e-fd48-a4b97734e2b9@emailplus.org> <2f95809c-8f0b-7d75-ca62-aeee11c6bee0@netcologne.de> <20230531142302.75ec742d@vepi2> <20230601111808.5ed7a9e3@vepi2> <20230605100825.78c4ac78@vepi2> <20230606150604.7cfbf6ac@vepi2> <74690341-bde3-47f2-8750-26a05578668d@orange.fr> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:mVWHCCF1BRrl0t24GFxdtxoIozmTEskxi7rQLHHLyKrFiaW/v5w Nq8JiV1Ga12SjL8FLhsOfxnq4s6lV3UnSAo8mzH11obNx9pLoqLiCdMUYHJJiX687aFV06x 1nXxtDb/Ig2beRtoRqhfFlw5NfHl7tbrie6S2djl/ucI/u7dQoEURMPe0PFjR6k47NOboct IY8wE2pAjOHFCykJdg1DQ== UI-OutboundReport: notjunk:1;M01:P0:fBFFO2Bt5mU=;GzLaHn0bz6S7rM41xmypU1s2Oxk mti8vtPDodBVH/m/d0H5w4O8Wtrfu3IbH4d60MchAbMY/3lQtcIdXblMADHiVjR9dr9B550IQ 5/hE9CTPZ1TW4Xf+Z1pwTptXuFiL9BeHfYJz573aW3x6aDvbZBmfOoVtPXzDk+ifPhFpN+2+l 6aBYgVEjOkZhH4/rpoJEdLY5PpBSSDBJlw4u1bLWab31CmBm5C88JHGvZlMwaoov3HtNLvTCc WJStsRoRoARy7r8MPt8Xtb/QyHV8kAcMkycwWraVbIhFmAdRWUJzY982dj5rbnGTFtvwCBPEh 0cX0R/XzuCixHgmDEFBT17j8Fzku+uP2BjUDDsEqDA+kVwCIoX3wPKsg8Lsa8tlGvHtrAx4wJ KKdpMO6/7SmaERI7F0OwhMhqvToma8s2L3qRkiKeuN21CPpGXrJERkEVYRBYbarB7j0iDhr4v U0ouXHeVH9r4ClXIGY7gVQcotEkdIqH93d0LVwnDYK5r8vnVFxUTzE4Gc/OUwrKlGw8unrfkK GuDFPYdsZ/5mYtL+Pv5XlzpRCBcy6Gmn2M5rroszb7XEM7L/JEJKwWWy5sR0Hfsv3MX2dl7KH PU4YyFzrX4sEdB+1/aGMP0BPpPD7SCOheMSzSUDKR4ysm1IXYJCN9H7kRVgXz2trO0EROmG7k P5PQAo07wtlHY4tsjllAoLf39Yuo68MZGo1Y9Yj9rrNECfoF37sibJPl3lO8Q9BdYRPBaE4RK gCM6JpUQudV3CoWJLH2hs8Y/vivJMwVMI1V3ncXpC5L8EFsDAv+0Tso+f789Z6x0ggKxEUmwI IO3caz9f2z4jFaKO2gm7rFkL5hrMb5KwRZSe68WCPGH431YwXaq6tLYoDsUw7ujQ4byX9XTI7 eSRzsp0LfvxHCeQf9PUSFUAWOjQbGNIGcHyLdvdS8wVIST2aXhyUzeG2T58ki1VH9+rP2cAhu CUp3qF6gzn2Z54dy9uM/GZtJ0m8= X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE,WINNER_SUBJECT autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Mikael, please find my answers inline. > > I understand. I would have been happy in the past when a client had as= much > > knowledge and structure than we already have. Under "Project goal" we = now > > have about 300 words. So we could add more. > Well, It wouldn't be really part of the goal, more how to reach that > goal. The "timeframe" question is possibly where it should go. Or if > you consider that the planning is a goal itself, it could be put here. The timeframe question accepts only a number. I.e. we can't plan there. > > What do you have in mind? > Something that breaks a big, risky thing to a set of smaller, manageable > ones. Something showing that the main problems (or some of them at > least) have been identified and that we have a path to solve them one by > one. > > > Like adding > > more bullet points to each item in the form of: > > - rebase existing implementation to current master > > - identify missing requirements > > - add tests for missing requirements > > - implement missing requirements to pass tests. > > ... > Well, this is a bit too general to be useful. Mhh, I don't suppose that the planning will be evaluated by software specialist. I therefore propose not to be too technical, but to stay on a project manager level. So how about we enumerate the bullets so that we th= en can put a project/milestone structure under each one like this (PD: person= day): 1.M1 assess open issues and refine planning (1-3 PDs) 1.M2 rebase to current master and adapt to recent changes in gfortran (1-3= PDs) 1.M3 identify missing requirements ... I need input here from Nicolas as I don't have an overview of what is needed. Therefore I am quite general. > > > Or are your targeting a more time based approach like: > > Milestone 1: shared mem coarrays merge to master in week 2 of proje= ct > > Milestone 2: finish research on general way for doing remote coarra= y > > access in alien structures to finish in week 1 of project > > ... > Maybe, but I would not emphasize the time constraints that much. I understand. But for our own planning we need a rough estimate. Therefore putting numbers to each milestone, will help a lot in planning. > I have done it below for the scalarizer simplification, which is what > for which the picture is the most clear in my mind regarding what to do > and how to do it. > Here it is, with the expected number of weeks (that's 3 days for me) to > do it: > - Add optional scalarization block. (1 week) > - Setup multiple expression usage (in case of multiple loops) in a > more clear way. (3 weeks) > - Move array and loop bounds setup to an opaque "start scalarization" > function (3 weeks) > - Make scalarization independant on previous setup of array > information and move setup code from "start scalarization" to "finish > scalarization" (5 weeks) > - Initialize array information inside the gfc_conv_expr* functions and > remove preliminary walking of expressions (4 weeks) > > I hope that's not too technical to be put in the application form. :-) Removing technical speech is not the problem... But I like the plan although I wouldn't know what to do in each case. > > Mikael Morin @ ??? -- Maintained/Contributed to the scalarizer. Experi= enced > > in gfortran development and component dependencies. > > > I'm not affiliated to any company, university or organization. Just > myself. :-) Sorry, I did not mean any insult. What do you prefer? "not affiliated" or "private", ...? Regards, Andre =2D- Andre Vehreschild * Email: vehre ad gmx dot de