From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Wileam Yonatan Phan <wileamyp@outlook.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"fortran@gcc.gnu.org List" <fortran@gcc.gnu.org>
Subject: Re: GSoC Blog Post 0 - GCCprefab build system
Date: Mon, 13 Jun 2022 12:59:01 +0100 [thread overview]
Message-ID: <CAH6eHdT=jSq-2zJ0gYqpXaVGNvuUF1Kvun4bWyodQ1PQN_d+hw@mail.gmail.com> (raw)
In-Reply-To: <BY5PR14MB391160D344B74F3D6A8D203BCEAB9@BY5PR14MB3911.namprd14.prod.outlook.com>
On Mon, 13 Jun 2022 at 02:51, Wileam Yonatan Phan via Gcc
<gcc@gcc.gnu.org> wrote:
>
> Hi everyone,
>
> This weekend marks the end of the community bonding period for GSoC '22, and
> here’s my progress so far with the GSoC project on Fortran DO CONCURRENT.
>
> I've initialized a GCC mirror on GitHub where I plan to track all patches that
> I will create during the GSoC:
> <https://github.com/wyphan/gfortran-do-concurrent>
>
> I met with Tobias over a MS Teams call on May 30, 2022. Together, we picked GCC
> PR# 102003 as a good starter issue to start delving into the Fortran parser in
> GCC. He also guided me through how to debug the compiler using gdb. Tobias,
> thanks a lot for spending some of your (technically) vacation time with me!
>
> In the meantime, I’ve implemented a simple build script system for GCC that I
> christen "GCCprefab". Before this build system existed, there are only two
> relatively easy ways to build GCC painlessly:
>
> 1. Using Spack package manager: `spack install gcc'
> 2. Using the install script for OpenCoarrays
> <https://github.com/sourceryinstitute/OpenCoarrays>
I disagree there are "only two" ways.
https://gcc.gnu.org/wiki/InstallingGCC describes an arguably much simpler way.
next prev parent reply other threads:[~2022-06-13 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 1:50 Wileam Yonatan Phan
2022-06-13 11:59 ` Jonathan Wakely [this message]
2022-06-13 13:34 ` Wileam Yonatan Phan
2022-06-13 15:26 ` Jonathan Wakely
2022-06-13 17:12 ` Wileam Yonatan Phan
2022-06-13 17:38 ` Jonathan Wakely
2022-06-14 0:37 ` Damian Rouson
2022-06-14 8:53 ` Jonathan Wakely
2022-06-14 11:16 ` Damian Rouson
2022-06-14 13:52 ` Wileam Yonatan Phan
2022-06-17 18:45 ` Bernhard Reutner-Fischer
2022-06-17 19:55 ` Jakub Jelinek
2022-06-18 19:24 ` Bernhard Reutner-Fischer
2022-06-17 20:07 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdT=jSq-2zJ0gYqpXaVGNvuUF1Kvun4bWyodQ1PQN_d+hw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=wileamyp@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).