On 08/05/2018 03:58, Joel Sherrill wrote: > On Mon, May 7, 2018 at 12:16 PM, Amaan Cheval <amaan.che...@gmail.com > <mailto:amaan.che...@gmail.com>> wrote: > > I'm not quite sure how GCC's releases work; it seems like GCC 8.1 has > already been released: > https://gcc.gnu.org/releases.html <https://gcc.gnu.org/releases.html> > https://ftp.gnu.org/gnu/gcc/gcc-8.1.0/ > <https://ftp.gnu.org/gnu/gcc/gcc-8.1.0/> > > However, the "gcc-7-branch" is still being pushed to: > https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/gcc-7-branch > <https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/gcc-7-branch> > > What would pushing to that branch entail? Is it simply to make > applying the patch to a 7.3 release easier? > > I only meant to make the patch to the RSB because: > - I'm not sure when the RSB will move to using GCC 8.1+ (we still use 7.3) > - It's better to have the RSB build the tooling the same for my dev > environment as the community will have, without needing manual patches > for building the tools > > I'm okay to just make a note about the patch if we'd rather not have > it in the RSB in case by the end of the port, GCC has released a > version including the patches which we can simply switch to using. > > Let me know if you prefer the latter! > > Unless gcc makes a release from the branch, we will have to continue > to have a patch.
A patch is fine. The cleaner and closer the patch is to a possible release the better. Once we have a release we can remove the patch. > > Chris is on holiday. Let's see what he wants done when he gets back. > I wish. I am here and working. I did go sailing on the weekend, but that was just a day of racing on Sydney harbour and the weather was so lovely, almost too good cause there was no wind and we all just sat about. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
