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 18:38:49 +0100 [thread overview]
Message-ID: <CAH6eHdSUHMYjY1tgA9veH5114dB-YXUgORCx-GD5HoptVJ9TwA@mail.gmail.com> (raw)
In-Reply-To: <BY5PR14MB3911B04CD26ECA2A546EBCC8CEAB9@BY5PR14MB3911.namprd14.prod.outlook.com>
On Mon, 13 Jun 2022, 18:12 Wileam Yonatan Phan, <wileamyp@outlook.com>
wrote:
>
>
> Yes, you are correct that the script currently uses the tip of the
> `releases/gcc-[version]` branches. Is that not the same as using the
> published
> tarballs on the FTP server?
No.
I _do_ notice that these branches only get pushed
> whenever a minor version or a patchlevel is released.
>
For the gcc-12 branch, it currently changes several times a week:
https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/releases/gcc-12
Releases only happen every few months, and even snapshots from the branch
happen only once a week.
Your config file uses the tip of the branch, which is not the "latest GCC
12 release" as it claims. It's something different depending when you
happen to run the script, not a release.
The latest GCC 12 release would be the releases/gcc-12.1.0 tag in Git.
>
next prev parent reply other threads:[~2022-06-13 17:39 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
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 [this message]
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=CAH6eHdSUHMYjY1tgA9veH5114dB-YXUgORCx-GD5HoptVJ9TwA@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).