Re: The future of i486 arch in Th

2015-01-31 Thread Witold Filipczyk
On Sat, Jan 31, 2015 at 12:35:28PM +0100, Jan Rękorajski wrote: > On Mon, 15 Dec 2014, Witold Filipczyk wrote: > > > > Kernel build for non-PAE i686 is what I want. > > Will be there today on i686, but only for head, so no vserver. Thanks. ___ pld-deve

Re: The future of i486 arch in Th

2015-01-31 Thread Jan Rękorajski
On Mon, 15 Dec 2014, Witold Filipczyk wrote: > On Mon, Dec 15, 2014 at 09:01:58PM +0100, Jan Rękorajski wrote: > > TL;DR Future of i486 is bleak, it's a strong candidate for removal. > > > > Proposal: remove i486 from Th. > > > > Rationale: > > > > It's increasingly more problematic to get ever

Re: The future of i486 arch in Th

2014-12-30 Thread Tomasz Pala
On Tue, Dec 30, 2014 at 20:22:01 +0100, Jan Rękorajski wrote: > If we have i686 arch we need to support i686 CPUs, not a random subset. We don't "need" to do anything. SSE2 is 13 years old now (and available for 11 years in AMD), I haven't seen unsupported CPUs in years. Hardware produced in tha

Re: The future of i486 arch in Th

2014-12-30 Thread Jan Rękorajski
On Tue, 30 Dec 2014, Tomasz Pala wrote: > +1 to abandoning i486 in current state (keeping last packages on FTP). > > On Mon, Dec 15, 2014 at 21:48:03 +0100, Jan Rękorajski wrote: > > >> Specifically: > >>Can RPM assume sse2 instructions and optimize digests/crypto to use > >> sse2? > > > >

Re: The future of i486 arch in Th

2014-12-30 Thread Tomasz Pala
+1 to abandoning i486 in current state (keeping last packages on FTP). On Mon, Dec 15, 2014 at 21:48:03 +0100, Jan Rękorajski wrote: >> Specifically: >> Can RPM assume sse2 instructions and optimize digests/crypto to use >> sse2? > > No 32bit AMD CPU has this. So, no, you can't do it uncon

Re: The future of i486 arch in Th

2014-12-16 Thread Jacek Konieczny
On 15/12/14 21:01, Jan Rękorajski wrote: > TL;DR Future of i486 is bleak, it's a strong candidate for removal. > > Proposal: remove i486 from Th. +1 Compiling IcedTea (Java) for i486 has been always problematic and took much longer than compiling it for other archs (hours of difference). Greets

Re: The future of i486 arch in Th

2014-12-15 Thread Jeffrey Johnson
On Dec 15, 2014, at 3:48 PM, Jan Rękorajski wrote: > On Mon, 15 Dec 2014, Jeffrey Johnson wrote: > >> I'm more interested in the lowest common denominator Intel architecture. >> >> Specifically: >> Can RPM assume sse2 instructions and optimize digests/crypto to use >> sse2? > > No 32bit

Re: The future of i486 arch in Th

2014-12-15 Thread Jan Rękorajski
On Mon, 15 Dec 2014, Jeffrey Johnson wrote: > I'm more interested in the lowest common denominator Intel architecture. > > Specifically: > Can RPM assume sse2 instructions and optimize digests/crypto to use > sse2? No 32bit AMD CPU has this. So, no, you can't do it unconditionally. We're

Re: The future of i486 arch in Th

2014-12-15 Thread Jeffrey Johnson
I'm more interested in the lowest common denominator Intel architecture. Specifically: Can RPM assume sse2 instructions and optimize digests/crypto to use sse2? 73 de Jeff On Dec 15, 2014, at 3:01 PM, Jan Rękorajski wrote: > TL;DR Future of i486 is bleak, it's a strong candidate for re

Re: The future of i486 arch in Th

2014-12-15 Thread Witold Filipczyk
On Mon, Dec 15, 2014 at 09:01:58PM +0100, Jan Rękorajski wrote: > TL;DR Future of i486 is bleak, it's a strong candidate for removal. > > Proposal: remove i486 from Th. > > Rationale: > > It's increasingly more problematic to get everything built on i486, some > packages explicitly say "no" to t

Re: The future of i486 arch in Th

2014-12-15 Thread Grzesiek
W dniu 15.12.2014 o 21:01, Jan Rękorajski pisze: TL;DR Future of i486 is bleak, it's a strong candidate for removal. Proposal: remove i486 from Th. Rationale: It's increasingly more problematic to get everything built on i486, some packages explicitly say "no" to this arch, some require hacks

The future of i486 arch in Th

2014-12-15 Thread Jan Rękorajski
TL;DR Future of i486 is bleak, it's a strong candidate for removal. Proposal: remove i486 from Th. Rationale: It's increasingly more problematic to get everything built on i486, some packages explicitly say "no" to this arch, some require hacks and strange workarounds, and other just silently fa