On 12/04/2021 14:52, Alexandre Oliva wrote:
> On Apr 12, 2021, Adhemerval Zanella wrote:
>
>> No, you are insinuating that the glibc community both as maintainer
>> and contributors acted in a hateful way regarding the 'joke'
>> removal. Sorry, but this is not true;
>
> Easy to say for someon
On Sun, Apr 11, 2021 at 10:43 PM Alexandre Oliva wrote:
>
> On Apr 11, 2021, Adhemerval Zanella wrote:
>
> > All the other active maintainers suggested you shouldn't have done that,
> > but you
> > ignored it anyway.
>
> How could I possibly have ignored something that hadn't happened yet?
>
> >
On Sun, Apr 11, 2021 at 8:06 PM Alexandre Oliva wrote:
>
> On Apr 11, 2021, Adhemerval Zanella wrote:
>
> > It was clear to me and others glibc maintainers that it was *you* who
> > bypass the consensus to *not* reinstate the “joke”.
>
> I think you wrote it backwards: what I did was to revert th
> Il giorno 11 apr 2021, alle ore 17:45, Alexandre Oliva via Gcc
> ha scritto:
>
> Remember how much hate RMS got in glibc land for something I did? I
> said I did it out of my own volition, I explained my why I did it, but
> people wouldn't believe he had nothing to do with it!
It was cle
On 24/11/2020 10:59, Siddhesh Poyarekar wrote:
> On 11/24/20 7:11 PM, Szabolcs Nagy wrote:
>> ideally fpclassify (and other classification macros) would
>> handle all representations.
>>
>> architecturally invalid or trap representations can be a
>> non-standard class but i think classifying the
On 30/04/2020 18:12, Jakub Jelinek wrote:
> On Thu, Apr 30, 2020 at 05:37:26PM -0300, Adhemerval Zanella via Gcc wrote:
>> Hi all, I would like to check if someone could help me figure out
>> an issue I am chasing on a libgomp patch intended to partially
>> address the
Hi all, I would like to check if someone could help me figure out
an issue I am chasing on a libgomp patch intended to partially
address the issue described at BZ#79784.
I have identified that one of the bottlenecks is the global barrier
used on both thread pool and team which causes a lof of ca
