On 23/08/18 21:56, Michael Ellerman wrote:

Christophe LEROY [off-list ref] writes:
=20

quoted

Le 23/08/2018 =C3=A0 12:36, Segher Boessenkool a =C3=A9crit=C2=A0:

quoted

On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:

quoted

The only small probl=C3=A8me I have is that some version of GCC seems =

to

quoted

quoted

quoted

complain about big memset() (132k and 256k ones). Is there a way to te=

ll

quoted

quoted

quoted

GCC we really want to do it ?

I'm not sure what you mean.  Complain, is that a warning, is that an er=

ror?

quoted

quoted

What does it say?  Do you have some example code to reproduce it?  Etc.

I saw the warnings in the checks at
https://patchwork.ozlabs.org/patch/957566/
Unfortunatly the link is now broken.

=20
ruscur/ajd any idea what happened to the snowpatch links here?

I think they've disappeared because our log rotation is too fast - I've=20
now upped it to 30 days. I guess over time we'll figure out what we need=20
in this regard, ideally we'd keep logs indefinitely but they're several=20
megs per build.

I've kicked off another build for this series and the links in Patchwork=20
should update to point to the new job when it's done (probably in the=20
next couple of hours).

--=20
Andrew Donnellan              OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com  IBM Australia Limited