GCC 7.5 November 14, 2019
GCC 9.2 August 12, 2019
GCC 9.1 May 3, 2019
GCC 8.3 February 22, 2019
GCC 7.4 December 6, 2018
GCC 6.5 October 26, 2018
GCC 8.2 July 26, 2018
GCC 8.1 May 2, 2018
GCC 7.3 January 25, 2018
GCC 5.5 October 10, 2017
GCC 7.2 August 14, 2017
GCC 6.4 July 4, 2017
GCC 7.1 May 2,
On Sun, Feb 16, 2020 at 11:36 AM Dennis Luehring wrote:
>
> GCC 7.5 November 14, 2019
> GCC 9.2 August 12, 2019
> GCC 9.1 May 3, 2019
> GCC 8.3 February 22, 2019
> GCC 7.4 December 6, 2018
> GCC 6.5 October 26, 2018
> GCC 8.2 July 26, 2018
> GCC 8.1 May 2, 2018
> GCC 7.3 January 25, 2018
> GCC 5.5
Am 16.02.2020 um 18:03 schrieb David Edelsohn:
https://gcc.gnu.org/develop.html#timeline
Thanks
any idea how to reintegrate (many) changes from a release/6.3.0 branch
back into mainline?
is there a tag or something where mainline was for short time in sync
with 6.3.0?
On Sun, Feb 16, 2020 at 12:19 PM Dennis Luehring wrote:
>
> Am 16.02.2020 um 18:03 schrieb David Edelsohn:
> > https://gcc.gnu.org/develop.html#timeline
> >
> Thanks
>
> any idea how to reintegrate (many) changes from a release/6.3.0 branch
> back into mainline?
>
> is there a tag or something whe
Am 16.02.2020 um 18:27 schrieb David Edelsohn:
On Sun, Feb 16, 2020 at 12:19 PM Dennis Luehring wrote:
>
> Am 16.02.2020 um 18:03 schrieb David Edelsohn:
> > https://gcc.gnu.org/develop.html#timeline
> >
> Thanks
>
> any idea how to reintegrate (many) changes from a release/6.3.0 branch
> back i
On Sun, Feb 16, 2020 at 12:36 PM Dennis Luehring wrote:
>
> Am 16.02.2020 um 18:27 schrieb David Edelsohn:
> > On Sun, Feb 16, 2020 at 12:19 PM Dennis Luehring wrote:
> > >
> > > Am 16.02.2020 um 18:03 schrieb David Edelsohn:
> > > > https://gcc.gnu.org/develop.html#timeline
> > > >
> > > Thanks
Am 16.02.2020 um 18:42 schrieb David Edelsohn:
If you are trying to forward-port your own, proprietary features into
a newer release of GCC for your own, internal use, that's your
responsibility.
that is my case, i ask for a meaningfull way of doing that
i could upgrade the 6.3 branch to 6.4,
On Sun, Feb 16, 2020 at 7:22 PM Dennis Luehring wrote:
>
> Am 16.02.2020 um 18:42 schrieb David Edelsohn:
> > If you are trying to forward-port your own, proprietary features into
> > a newer release of GCC for your own, internal use, that's your
> > responsibility.
>
> that is my case, i ask for
Am 17.02.2020 um 10:51 schrieb Richard Biener:
I would start merging the new feature ontop master to the point where
GCC 6 branched (so go _back_ in time) and only then start moving forward,
remaining on master.
good idea, thank you
