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

2020-02-17 Thread Richard Biener
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

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

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

GCC 8.4 Status Report (2020-02-17)

2020-02-17 Thread Jakub Jelinek
Status == It has been almost a year since GCC 8.3 has been released and GCC 8.4 release should have been released already, so we should concentrate on getting it out soon. Unfortunately we have two P1s, one of them is waiting for reporter's input, so we might as well just ignore it unless the

libc coordination list

2020-02-17 Thread Florian Weimer
There's a new mailing list for cross-libc coordination issues, hosted at Openwall: I'm including the test of the announcement below. Thanks, Florian Welcome to the libc-coord list! This list is intended to coordinate work on run-time l

Sua fatura chegou.

2020-02-17 Thread 430189 gcbcustomerservice
  Estimado cliente, gcc@gcc.gnu.org   Segue em anexo a sua fatura eletrônica do mês de fevereiro.   Fatura 17.02.2020(652KB).PDF  

Re: Matching and testing against smulhsm3

2020-02-17 Thread Marcus Geelnard
Hi Segher, Thanks for the analysis! On 2020-02-17 02:12, Segher Boessenkool wrote: 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   (mu

update github gcc mirror forks to the new repo?

2020-02-17 Thread Dennis Luehring
so the github gcc mirror is already using the new reposurgeon based git repo, that means that all the commit hashes etc. are different if someone forked this gcc mirror so easy pulling from the mirror isn't possible anymore - or am im wrong? is there any description how to "port" over github p