SOOL Hashes

a712557bc4d071895a30d5691395661c15d40f738e7090ea8ffc923e20d746ac2177374146a5699512a3a9f1d6e576ad4b070a78233d01ec9493f88e8564a198 SOOL Presentation - in depth.pdf 532f84ce40ed291d7c00b3714904300c2bd538f836cb3bdf5b28003eb0c19ebdcf1f9faf0fabf8a3be6ecc6f7c29cfedd67464e467f98742445e0b2d555145d0 SOOL P

Re: Has FSF stopped processing copyright paperwork

Le 26 avr. 2021 à 23:31, Gerald Pfeifer mailto:ger...@pfeifer.com>> a écrit : I got notified of copyright assignments related to GCC by copyright-cl...@fsf.org on April 5th, April 8th, April 22nd (two instances) and April 26th (today). So the process seems to be

Re: Has FSF stopped processing copyright paperwork

On Mon, 26 Apr 2021, Romain GEISSLER via Gcc wrote: > Few weeks later, I would like to know if anyone on the list knows if FSF is > still processing copyright assignment these days. Basically shall people > willing to sign one just have to be patient as processing is still on-going, > or if process

Re: Has FSF stopped processing copyright paperwork

On Mon, 2021-04-26 at 21:01 +, Romain GEISSLER via Gcc wrote: > So anyone has some insider information about the FSF copright > assignment process ? I have no insider information but you can try asking on gnu-prog-disc...@gnu.org (I think that list is open) I assume you're communicating with

Re: Has FSF stopped processing copyright paperwork

On Apr 26 2021, Romain GEISSLER via Gcc wrote: > So anyone has some insider information about the FSF copright assignment > process ? I don't have insider information, but I just received a confirmation of a copyright assignment for glibc. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG

Re: Has FSF stopped processing copyright paperwork

Hi, (Please note that this mail is *NOT* about the recent discussions about the relationship with the FSF. AFAIK to date FSF copyright assignment is still required to contribute to gcc and this request is solely about how to have one signed.) Few weeks later, I would like to know if anyone on the

Re: State of AutoFDO in GCC

On Mon, Apr 26, 2021 at 06:40:56PM +, Hongtao Yu wrote: >Andi, thanks for pointing out the perf script issues. Can you please >elaborate a bit on the exact issue you have seen? We’ve been using >specific output of perf script such as mmap, LBR and callstack events >filtered by p

Re: State of AutoFDO in GCC

Andi, thanks for pointing out the perf script issues. Can you please elaborate a bit on the exact issue you have seen? We’ve been using specific output of perf script such as mmap, LBR and callstack events filtered by process id. It works fine so far but may certainly hit issues in the future wi

Re: State of AutoFDO in GCC

On Mon, Apr 26, 2021 at 11:00 AM Andi Kleen wrote: > >There are multiple directional changes in this new tool: > >1) it uses perf-script trace output (in text) as input profile data; > > I suspect this will break regularly too > > (I personally did numerous changes to perf script output,

Re: State of AutoFDO in GCC

>There are multiple directional changes in this new tool: >1) it uses perf-script trace output (in text) as input profile data;  I suspect this will break regularly too (I personally did numerous changes to perf script output, and also wrote a lot of parsing scripts) The perf script outp

[walter thierry]RE:Journée fantastique

Je l'ai aimé❗ http://9w6ed2v.worknumbermethod.work/d10 walter thierry loyalement

Re: State of AutoFDO in GCC

On Mon, Apr 26, 2021 at 8:12 AM Andi Kleen wrote: > Jan Hubicka writes: > > > > Is there a way to get this working w/o using older perf? > > It's usually rather simple to fix up autofdo for new perf. > I did it before here > > https://github.com/andikleen/autofdo/commits/perf4-3 > > I think it w

gcc-12-20210426 is now available

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

gcc-11-20210426 is now available

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

Re: gcc-11-20210425 is now available

On Mon, 26 Apr 2021, Arseny Solokha via Gcc wrote: > Hi, > > > Snapshot gcc-11-20210425 is now available on > > https://gcc.gnu.org/pub/gcc/snapshots/11-20210425/ > > and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. > > > > This snapshot has been generated from the GCC 1

Re: State of AutoFDO in GCC

Jan Hubicka writes: > > Is there a way to get this working w/o using older perf? It's usually rather simple to fix up autofdo for new perf. I did it before here https://github.com/andikleen/autofdo/commits/perf4-3 I think it would work always if it just ignored unknown records (which is quite p

Re: "musttail" statement attribute for GCC?

On 26/04/2021 14:49, Iain Sandoe via Gcc wrote: Alexander Monakov wrote: On Fri, 23 Apr 2021, Josh Haberman via Gcc wrote: On Fri, Apr 23, 2021 at 1:10 PM Iain Sandoe wrote: I did try to use it this ^ for GCC coroutines (where such a guarantee is pretty important) However, the issue t

Re: "musttail" statement attribute for GCC?

Alexander Monakov wrote: On Fri, 23 Apr 2021, Josh Haberman via Gcc wrote: On Fri, Apr 23, 2021 at 1:10 PM Iain Sandoe wrote: I did try to use it this ^ for GCC coroutines (where such a guarantee is pretty important) However, the issue there is that not all targets support indirect tail

Re: "musttail" statement attribute for GCC?

On Fri, 23 Apr 2021, Josh Haberman via Gcc wrote: > On Fri, Apr 23, 2021 at 1:10 PM Iain Sandoe wrote: > > I did try to use it this ^ for GCC coroutines (where such a guarantee is > > pretty important) > > > > However, the issue there is that not all targets support indirect tailcalls. > > I'm n