Hi all,
Do we still have users running 32-bit machines? It would reduce the load on
hydra significantly if we could drop support for i686, though of course if
people are still relying on it we shouldn't make the change yet.
~Shea
___
nix-dev mailing l
I encountered an i686 user just the other day! I don't use it personally,
but having solid support in Nix was fantastic, especially because older,
32-bit machines tend to be slower, which makes Nix's binary caching
functionality even more important.
On Mon, May 11, 2015 at 6:36 PM, Shea Levy wro
Maybe it would make more sense to only build the i686 builds if our tested
set of x86_64 binaries build correctly. We would still release with both
but it would cut down on a lot of redundant failures.
On Mon, May 11, 2015 at 3:39 PM Ryan Trinkle wrote:
> I encountered an i686 user just the othe
Is there a way to get stats on which binary cache hashes are being
retrieved? Would be interesting to see what percentage is i686 and scale
build shares accordingly.
On Mon, May 11, 2015 at 6:36 PM, Shea Levy wrote:
> Hi all,
>
> Do we still have users running 32-bit machines? It would reduce th
I'm relying on these builds on my home laptop.
On Mon, May 11, 2015 at 11:36 PM, Shea Levy wrote:
> Hi all,
>
> Do we still have users running 32-bit machines? It would reduce the load on
> hydra significantly if we could drop support for i686, though of course if
> people are still relying on it
I'm on x86_64 and use some of those for running games (mostly what the steam
package already pulls in, plus a few more that were needed for specific games).
The idea to only build them after x86_64 sounds pretty good. Actually, are all
packages build together with the tests or only after they pa
I'm still using i686 on my Atom based NAS.
It would be okay for me if only nixos-minimal was build for i686.
Nathan.
On Tue, May 12, 2015 at 8:34 AM Tomasz Kontusz
wrote:
> I'm on x86_64 and use some of those for running games (mostly what the
> steam package already pulls in, plus a few more
+1
This seems like a good idea.
On 12 May 2015 at 06:45, William Kennington wrote:
> Maybe it would make more sense to only build the i686 builds if our tested
> set of x86_64 binaries build correctly. We would still release with both
> but it would cut down on a lot of redundant failures.
>
>
I use 32 bit a lot.
First of all, I use it on some old machines with 32bit hardware.
But, more importantly, I use it regularly on virtuabox and xen virtual
machines.
In my experience, for most of my use cases the 32bit require less memory
(which is often not abundant on virtual instances) and it is
My experience is equal with Marco, about memory and my usage of i686. i686
is important for me too.
On Tue, May 12, 2015 at 11:43:47AM +0200, Marco Maggesi wrote:
> I use 32 bit a lot.
> First of all, I use it on some old machines with 32bit hardware.
> But, more importantly, I use it regularly on
Hi,
same here.
Many interpreted languages (like Python) are affected by this as they tend to
be quite pointer-happy. As pointer-size doubles from 32bit to 64bit we find
that in most applications we have about 70% increase when moving to 64-bit
ending up with 1.7 as much memory as before. So we
amd32 should be ready in the kernel and gcc/glibc. We just need someone to
prepare nix/nixpgks/nixos for this. :)
On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote:
> Hi,
>
> same here.
>
> Many interpreted languages (like Python) are affected by this as they tend to
> be quite p
By amd32 do you mean amd64 with 32 bit pointers?
"Lluís Batlle i Rossell" napisał:
>amd32 should be ready in the kernel and gcc/glibc. We just need someone
>to
>prepare nix/nixpgks/nixos for this. :)
>
>On Tue, May 12, 2015 at 12:05:29PM +0200, Christian Theune wrote:
>> Hi,
>>
>> same here.
>>
Yes. Maybe it got renamed... It used to be named 'amd32'.
On Tue, May 12, 2015 at 12:45:36PM +0200, Tomasz Kontusz wrote:
> By amd32 do you mean amd64 with 32 bit pointers?
>
> "Lluís Batlle i Rossell" napisał:
> >amd32 should be ready in the kernel and gcc/glibc. We just need someone
> >to
> >p
On 12/05/15 12:49, Lluís Batlle i Rossell wrote:
> Yes. Maybe it got renamed... It used to be named 'amd32'.
It's called x32:
http://en.wikipedia.org/wiki/X32_ABI
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev mailing list
On Tue, May 12, 2015 at 01:21:59PM +0200, Eelco Dolstra wrote:
> On 12/05/15 12:49, Lluís Batlle i Rossell wrote:
>
> > Yes. Maybe it got renamed... It used to be named 'amd32'.
>
> It's called x32:
>
> http://en.wikipedia.org/wiki/X32_ABI
Thank you!
So this thread could end up in an extra nix
Hi.
On 05/12/2015 12:45 AM, William Kennington wrote:
> Maybe it would make more sense to only build the i686 builds if our
> tested set of x86_64 binaries build correctly.
This seems the best suggestion I know of now. It shouldn't be difficult
to implement, and it also makes important x86_64 par
17 matches
Mail list logo