Re: GCC Multi-Threading Ideas

On 1/23/20 12:19 PM, Nicholas Krause wrote: On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote: On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote: Greetings All, Unfortunately due to me being rather busy with school and other things I will not be able to post my article to the

Re: GCC Multi-Threading Ideas

On 1/23/20 12:19 PM, Nicholas Krause wrote: On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote: On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote: Greetings All, Unfortunately due to me being rather busy with school and other things I will not be able to post my article to the

Re: Merges from release branches to vendor tracking branches

On 1/23/20 12:09 PM, Peter Bergner wrote: > On 1/23/20 4:29 AM, Jakub Jelinek wrote: >> so it is not a fast forward merge and we have the requirement that >> From-SVN: shouldn't appear in commit logs of new commits. > > So I just did "git merge releases/gcc-9" into our branch and I'm not > seeing

Re: GNU Tools Cauldron 2020

On Thu, Jan 23, 2020 at 10:20 AM Olivier Hainque wrote: > > Hello, > > We are pleased to invite you all to the next GNU Tools Cauldron, > taking place in Paris on June 12-14, 2020. > > As for the previous instances, we have setup a wiki page for > details: > > https://gcc.gnu.org/wiki/cauldron

Re: GNU Tools Cauldron 2020

* Alfred M. Szmidt: >Please feel free to share with other groups as appropriate. > > The form requires non-free software and Google malware. Please do not > recommend that people share such things on GNU project lists. The message you quoted also said: | If unable to use this form, please v

Re: GNU Tools Cauldron 2020

Please feel free to share with other groups as appropriate. The form requires non-free software and Google malware. Please do not recommend that people share such things on GNU project lists.

GNU Tools Cauldron 2020

Hello, We are pleased to invite you all to the next GNU Tools Cauldron, taking place in Paris on June 12-14, 2020. As for the previous instances, we have setup a wiki page for details: https://gcc.gnu.org/wiki/cauldron2020 The conference is free to attend, registration in advance is require

Re: GNU Tools Cauldron 2020

Hi Olivier, I would like to be part of the organising committee. I am from Nairobi, Kenya. Thanks and regards, Fadhili Juma. On Thu, Jan 23, 2020 at 9:30 PM Olivier Hainque wrote: > Hello, > > We are pleased to invite you all to the next GNU Tools Cauldron, > taking place in Paris on June 12-1

Re: Merges from release branches to vendor tracking branches

On 1/23/20 4:29 AM, Jakub Jelinek wrote: > Just FYI if somebody needs to do something similar, I needed to do a merge > from origin/releases/gcc-9 to our vendor branch - > refs/vendors/redhat/heads/gcc-9-branch > This branch has some extra commits origin/releases/gcc-9 branch doesn't > have, This

Re: GCC Multi-Threading Ideas

On 1/23/20 3:39 AM, Allan Sandfeld Jensen wrote: On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote: Greetings All, Unfortunately due to me being rather busy with school and other things I will not be able to post my article to the wiki for awhile. However there is a rough draft

Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"

On 23/01/2020 16:46, Joseph Myers wrote: On Thu, 23 Jan 2020, Richard Earnshaw (lists) wrote: Perhaps we should restrict that to a single line, ie only horizontal white space. Our commit style isn't really that free-form when citing bugs. Or perhaps require [:.]?\w after the number (ie an opt

Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"

On Thu, 23 Jan 2020, Richard Earnshaw (lists) wrote: > Perhaps we should restrict that to a single line, ie only horizontal white > space. Our commit style isn't really that free-form when citing bugs. Or > perhaps require [:.]?\w after the number (ie an optional period or colon and > then some

Re: Merges from release branches to vendor tracking branches

On Thu, 23 Jan 2020, Jakub Jelinek wrote: > Just FYI if somebody needs to do something similar, I needed to do a merge > from origin/releases/gcc-9 to our vendor branch - > refs/vendors/redhat/heads/gcc-9-branch > This branch has some extra commits origin/releases/gcc-9 branch doesn't > have, so

Re: [PATCH] wwwdocs: document scripts to access personal and vendor spaces

On 21/01/2020 18:58, Richard Earnshaw (lists) wrote: This patch documents some of the scripts that I've published for managing the personal and vendor spaces on the server.  It also covers some of the other features that those scripts enable, so that it's all in one place.  This is a complete r

Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"

On 23/01/2020 15:28, Jakub Jelinek wrote: On Thu, Jan 23, 2020 at 04:23:01PM +0100, Thomas Schwinge wrote: Hi! On 2020-01-23T12:46:24+, Andrew Stubbs wrote: I've committed this patch to fix a bug in the OpenMP argument parsing.

Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"

On Thu, Jan 23, 2020 at 04:23:01PM +0100, Thomas Schwinge wrote: > Hi! > > On 2020-01-23T12:46:24+, Andrew Stubbs wrote: > > I've committed this patch to fix a bug in the OpenMP argument parsing. > > . > > Why did "the system"

Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"

Hi! On 2020-01-23T12:46:24+, Andrew Stubbs wrote: > I've committed this patch to fix a bug in the OpenMP argument parsing. . Why did "the system" decided to annotate ? For obvious reasons, there are

Merges from release branches to vendor tracking branches

Hi! Just FYI if somebody needs to do something similar, I needed to do a merge from origin/releases/gcc-9 to our vendor branch - refs/vendors/redhat/heads/gcc-9-branch This branch has some extra commits origin/releases/gcc-9 branch doesn't have, so it is not a fast forward merge and we have the r

Re: GCC Multi-Threading Ideas

On Montag, 20. Januar 2020 20:26:46 CET Nicholas Krause wrote: > Greetings All, > > Unfortunately due to me being rather busy with school and other things I > will not be able to post my article to the wiki for awhile. However > there is a rough draft here: > https://docs.google.com/document/d/1p