Re: Matching and testing against smulhsm3

2020-02-16 Thread Segher Boessenkool
Hi! On Sun, Feb 16, 2020 at 09:52:12PM +0100, Marcus Geelnard wrote: >   (define_insn "smulhshi3" >     [(set (match_operand:HI 0 "register_operand" "=r") >   (truncate:HI >     (ashiftrt:SI >   (mult:SI >     (sign_extend:SI (match_operand:HI

gcc-10-20200216 is now available

2020-02-16 Thread gccadmin
Snapshot gcc-10-20200216 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20200216/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: Matching and testing against smulhsm3

2020-02-16 Thread Marcus Geelnard
On 2020-02-09 19:02, Segher Boessenkool wrote: On Sun, Feb 09, 2020 at 12:15:03PM +0100, m wrote: On 2020-02-07 16:44, Segher Boessenkool wrote:   (define_insn "smulhshi3"     [(set (match_operand:HI 0 "register_operand" "=r")   (truncate:HI     (ashiftrt:SI   (mult:SI    

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread Dennis Luehring
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,

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread David Edelsohn
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

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread Dennis Luehring
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

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread 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 into mainline? > > is there a tag or something whe

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread Dennis Luehring
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?

Re: Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread David Edelsohn
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

Is ther document that describes how the "braching/fixing" on releases is done

2020-02-16 Thread Dennis Luehring
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,