From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by sourceware.org (Postfix) with ESMTPS id 805C53858D37 for ; Wed, 31 May 2023 03:46:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 805C53858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=emailplus.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=emailplus.org Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9A23E5C01AF; Tue, 30 May 2023 23:46:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 30 May 2023 23:46:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emailplus.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm1; t=1685504808; x=1685591208; bh=bBzaAY2hzzMXNcY/QNZMSoAZY 973DRMOGPEZC3aIff4=; b=q18pGMzp/TCN5phbzE5Zh3HeMDbdtH2pkV0i7a3s6 r8FUOZ1sxNXrNsF4phrYJXEavcoM2wPGzTDQxt6DNfcJxgfGszqPXjB0pkeTK/70 UGjbxE+4a9z+skFl1kuWKYEcQ1UQ6NB/WnyYz7qanS3aAn1K5MQLNpJexysB2s68 nCVkmdp/xPUGrfcIzR3rkQvCK0rCmd/8+hkYMve4yBFcmM3ixAru0ke5IPgcMJuh 1NM4IOrcBnwcRTDJXYRUTdUt2Q8lAzOOeg95dz3iZufI/RJRy8DKKVbbJiSZC5jO r9grK3ocIrsKbinEybzSJ+Q6UNluC+kTPiwMQfjOvyCGA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1685504808; x=1685591208; bh=bBzaAY2hzzMXNcY/QNZMSoAZY973DRMOGPE ZC3aIff4=; b=vvreL8hpxn6KZRNrXgj4WzBQyvpKyZE26K4GoDp6j+dK1wsiLxu yNvoyVD1OSFkmUAxdFODfR0hb8PxgrEP6DdqZHKN0HESRB9erXMn5QatNyBBpuZS LVTLXYueaSzxxt6HZ8jvjYLsHmKJLw3ugrmj0DkC8YuvGuWloFEuDz16vxS4ovd+ CRgxxQqtQtyV2NdL1VuF3o5x9OuFgvy5nBuux4hAE9l1/jZgMIPZszKgmUUMvltp ZvmMrKtVavGAZ8Nk6SOm/7Oiw77GEJaRThQCZWsGxJDUU94qZv0KC8lXXriyY130 FLxFfS6xKf4Zu3GEpps1iMyi6IP1F7rMVcg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeekkedgjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlqddutddmnecujfgurhepkfffgggfvfevfhfhufgjtgfgsehtkeer tddtfeejnecuhfhrohhmpeeuvghnshhonhcuofhuihhtvgcuoegsvghnshhonhgpmhhuih htvgesvghmrghilhhplhhushdrohhrgheqnecuggftrfgrthhtvghrnhepjeeltdfftdek jeduiefhfeeileejgfetiefgjeegheehgeetgeehgefhvdekvedtnecuffhomhgrihhnpe gtphdvkhdrohhrghdplhgslhdrghhovhenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpegsvghnshhonhgpmhhuihhtvgesvghmrghilhhplhhush drohhrgh X-ME-Proxy: Feedback-ID: ic1e8415a:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 30 May 2023 23:46:44 -0400 (EDT) Message-ID: <5bde7c1f-3524-7f2e-fd48-a4b97734e2b9@emailplus.org> Date: Wed, 31 May 2023 06:46:41 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 To: Thomas Koenig , Andre Vehreschild , Jerry D Cc: Mikael Morin , Paul Richard Thomas , GCC-Fortran-ML , Lexi Pimenidis 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> Content-Language: en-US From: Benson Muite Subject: Re: Possible funding of gfortran work In-Reply-To: <2fa3240f-fbb8-23b6-2a10-24f9a415f729@netcologne.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00,BODY_8BITS,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,KAM_SHORT,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPAM_BODY,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE,WINNER_SUBJECT autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 5/30/23 23:08, Thomas Koenig via Fortran wrote: > On 30.05.23 15:32, Andre Vehreschild wrote: >> Hi all, >> >> thank you for all your input. I have read the funding requirements and >> checked >> out the application form. We have to agree on a project goal and >> describe why >> it is critical to fund this project. >> >> Let me try a first shot on this: >> >> - Title: >> >> GFortran-Improvement >> >> - Abstract: >> >> Enable the free gfortran compiler to support contemporary language >> paradigms. >> >> - Dependencies (on the project as well as projects that depend on the >>    technology) >> >> Does any one have a convincing project that uses contemporary Fortran? > > CP2K is an example, it's open source and written in Fortran. > > https://www.cp2k.org/ > > >> Project goal (max 900 words!): >> >> * Complete language intrinsic parallel programming paradigm coarrays. >> This >>    includes completing native coarray support (thread based). As well as >>    refactoring of the library based  coarray approach to support >> coarrays in >>    modules. I.e. research on how to support the use of coarrays in >> modules that >>    are not aware of coarrays (not compiled with its support enabled). > Is distributed memory support for co-arrays of interest as well? There is a lot of code that uses MPI (for which there is some push for using more modern Fortran features), and there are also other libraries such as GASPI. > The current work is process-based, and there is no problem that we see > about library code. > > What about this? > > * Fortran has a safe and intuitive method for parallel execution, >   coarrays. There is currently no efficient implementation for >   multi-core CPUs on a freely available compiler.  The goal is to bring >   the existing, process-based shared memory implementation on a branch >   into gfortran mainline as an experimental, but useful feature. > > I also would not promise complete coarray support by project's end. > This would include teams, which are scary :-) > > Having a useful > > (There is Intel, which is dog-slow, and there is NAG, which costs > money). Is this also expected in Flang? See: https://crd.lbl.gov/divisions/amcr/computer-science-amcr/class/research/caffeine/ https://crd.lbl.gov/divisions/amcr/computer-science-amcr/class/research/caffeine/ Probably good to make a case for two open source compilers. > >> * Complete standard compliance from Fortran 2003 onwards. Esp. fixing >>    finalization of partially derived types (PDTs) and issues in the >> associate >>    command. > > Again, we should not promise what we cannot deliver. > >> * Ensure maintainability of gfortran by cleaning up/refactoring APIs >> including >>    the scalarizer. Improve the single responsibility pattern's (SRP) >> use by, >>    e.g., ensuring the parser does no longer parts of the resolve >> stage. The goal >>    is not only to separate responsibilities but also to get clearer error >>    messages and with that improve user-friendliness. >> >> Why is it critical to fund this project (300 words max)? > >> Improving the freely available gfortran compiler to support state of >> the art >> parallelism and language paradigms as well as removing bugs and ensuring >> standard compliance will allow existing codes to be compiled more >> reliably. >> Furthermore is the lack of support for the newer language paradigms >> preventing >> the use of Fortran in current projects. Developing in contemporary >> Fortran needs >> commercial compilers (that support these paradigms already), which >> leads to >> dependencies on those. > > Fortran remains one of the premier language for science, especially for > high-performance computing and fields like quantum chemistry or > computational fluid dynamics. > > gfortran is the default Fortran compiler on Linux systems, and lack of > features and bugs in in gfortran hinder adoption of more modern, safer > and more efficient language features. The project has been almost > entirely volunteer-driven so far, but is currently suffering from > a lack of active developers.  Funding will motivate experienced > gfortran developers who have reduced their contributions to return > to the project and advance it substantially. > > Any possibilities for new contributors to participate? >> This is what I propose for a start. I welcome everyone to participate >> and make >> the goal or the reasoning more elaborate. We may propose the funding >> request in >> English or in German. When no one participates, I am tempted to >> propose it in >> German, as that being my first language, I feel more confident in it. > > Make it English, all people here on the list should be able to follow. > >> The company Badger Systems GmbH, Cologne, DE, I am working for will >> support in >> project and bureaucratic management and is willing to act as the >> proposer of >> this funding request. We of course will be profiting from this. >> >> Any input is welcome. Feel free to ask, comment, agree, disagree (only >> when you >> propose something better) or just acknowledge. > > One thing I did not find at a cursory glance is how the project funding > would be distributed, and under which conditions. > > Did you find anything on the website? > > Best regards > >     Thomas >