Erik de Castro Lopo wrote:
> Thanks for the confirmation. Måns Rullgård has dug a little deeper
> and confirmed this as a GCC bug. I'm happy to raise a but there
> and let the GCC people sort it out.
I raised it as a bug agains Debian's gcc as I didn't know how
that would be different from upstre
Neil Williams wrote:
> > If so I would appreciate it if you could clone this git repo, read the
> > Readme.d, run the test:
> >
> > CC=gcc-4.9 make clean check
> >
> > and let me know the results. If your Aarch64 machine is already
> > connected to the 'net and has gcc-4.9 installed, the tes
On Fri, 5 Dec 2014 23:27:57 -0800
Erik de Castro Lopo wrote:
> Anybody have access to real #Aarch64 hardware running #Debian?
Yes. Using LAVA.
https://staging.validation.linaro.org/scheduler/job/114969/definition
(That job uses my SSH public key and needs access inside LAVA, but it
shows the b
Hi all,
Anybody have access to real #Aarch64 hardware running #Debian?
If so I would appreciate it if you could clone this git repo, read the
Readme.d, run the test:
CC=gcc-4.9 make clean check
and let me know the results. If your Aarch64 machine is already connected
to the 'net and has gcc
4 matches
Mail list logo