On Friday 28 July 2017 07:54:43 Adrian Bunk wrote:
> On Fri, Jul 28, 2017 at 08:30:30AM +, Riku Voipio wrote:
> > On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote:
> > > On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > > > > Does this emulation take a
On Fri, Jul 28, 2017 at 08:30:30AM +, Riku Voipio wrote:
> On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote:
> > On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > > > Does this emulation take a considerable performance hit, as opposed
> > > > to
> > > > running on
On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote:
> On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > > Does this emulation take a considerable performance hit, as opposed
> > > to
> > > running on armhf hardware/kernel, where the instruction doesn't
> > > appear
> > >
On 2017-07-27, Riku Voipio wrote:
> On Wed, Jul 05, 2017 at 12:51:08PM -0700, Vagrant Cascadian wrote:
>> Some of the reproducible builds armhf nodes are actually arm64 capable
>> machines, running an arm64 kernel build. When haskell related packages
>> get built, I get a tremendous number of
On Wed, Jul 05, 2017 at 12:51:08PM -0700, Vagrant Cascadian wrote:
> Some of the reproducible builds armhf nodes are actually arm64 capable
> machines, running an arm64 kernel build. When haskell related packages
> get built, I get a tremendous number of messages on to the console:
>
> "ghc"
On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > Does this emulation take a considerable performance hit, as opposed
> > to
> > running on armhf hardware/kernel, where the instruction doesn't
> > appear
> > to be listed as deprecated?
>
> I'd expect the kernel-emulated
> Does this emulation take a considerable performance hit, as opposed to
> running on armhf hardware/kernel, where the instruction doesn't appear
> to be listed as deprecated?
I'd expect the kernel-emulated instruction to be much slower than any
non-emulated instruction, but the overall effect on
I wouldn't take the message too seriously, just Google it:
https://www.google.com/search?q=%22uses+deprecated+CP15+Barrier+instruction%22=utf-8=utf-8
On 7/5/17, Vagrant Cascadian wrote:
> Some of the reproducible builds armhf nodes are actually arm64 capable
> machines,
Some of the reproducible builds armhf nodes are actually arm64 capable
machines, running an arm64 kernel build. When haskell related packages
get built, I get a tremendous number of messages on to the console:
"ghc" (13126) uses deprecated CP15 Barrier instruction at 0xefadd224
In the
9 matches
Mail list logo