Greetings Everyone,
I've been looking for a while, but no luck. Is there a table somewhere
that summarizes the different architecture names like i386, i586, i686,
amd64, ia64, and so on along with the criteria for hardware qualifying
under that name?
e.g. Does i686 mandate SSE2?
PS I am not on t
Am Dienstag, den 27.04.2010, 12:45 -0700 schrieb Kip Warner:
> Greetings Everyone,
>
> I've been looking for a while, but no luck. Is there a table somewhere
> that summarizes the different architecture names like i386, i586, i686,
> amd64, ia64, and so on along with the criteria for hardware qual
On Tue, 2010-04-27 at 22:16 +0200, Benjamin Drung wrote:
> Am Dienstag, den 27.04.2010, 12:45 -0700 schrieb Kip Warner:
> > Greetings Everyone,
> >
> > I've been looking for a while, but no luck. Is there a table somewhere
> > that summarizes the different architecture names like i386, i586, i686,
On Tue, 2010-04-27 at 12:45 -0700, Kip Warner wrote:
> Greetings Everyone,
>
> I've been looking for a while, but no luck. Is there a table somewhere
> that summarizes the different architecture names like i386, i586, i686,
> amd64, ia64, and so on along with the criteria for hardware qualifying
>
On Tue, 2010-04-27 at 13:40 -0700, Kip Warner wrote:
> On Tue, 2010-04-27 at 22:16 +0200, Benjamin Drung wrote:
> > Am Dienstag, den 27.04.2010, 12:45 -0700 schrieb Kip Warner:
> > > Greetings Everyone,
> > >
> > > I've been looking for a while, but no luck. Is there a table somewhere
> > > that s
On Tue, Apr 27, 2010 at 12:45:30PM -0700, Kip Warner wrote:
> Greetings Everyone,
>
> I've been looking for a while, but no luck. Is there a table somewhere
> that summarizes the different architecture names like i386, i586, i686,
> amd64, ia64, and so on along with the criteria for hardware quali
On Tue, 2010-04-27 at 21:29 +, brian m. carlson wrote:
> As far as uname, not all machines that output i686 will support SSE2.
> Your assumption should be that i686 == Pentium Pro, with the caveat
> that
> not all i686 machines support cmov (some Via chips do not).
Thanks. If I was writing so
On Tue, 2010-04-27 at 21:43 +0100, Ben Hutchings wrote:
> It must be 'i386'.
But i386 includes machines like the 486 and the Pentium Pro that did not
have SSE2 instruction set.
If I was writing something for a 32-bit machine with SSE2 instruction
set, what would be the most appropriate architectu
Am Dienstag, den 27.04.2010, 14:45 -0700 schrieb Kip Warner:
> On Tue, 2010-04-27 at 21:43 +0100, Ben Hutchings wrote:
> > It must be 'i386'.
>
> But i386 includes machines like the 486 and the Pentium Pro that did not
> have SSE2 instruction set.
>
> If I was writing something for a 32-bit machi
On Wed, 2010-04-28 at 00:32 +0200, Benjamin Drung wrote:
>
> The best solution would be autodetection of SSE2 on runtime. That can
> be
> done with a few lines of code.
You're right, that can indeed be done with a few lines of code. e.g.
cpuid instruction. The problem is that you then have to pe
On Mi, Apr 28, 2010 at 02:07:56 (CEST), Kip Warner wrote:
> On Wed, 2010-04-28 at 00:32 +0200, Benjamin Drung wrote:
>>
>> The best solution would be autodetection of SSE2 on runtime. That can
>> be
>> done with a few lines of code.
>
> You're right, that can indeed be done with a few lines of c
Reinhard Tartler writes:
> On Mi, Apr 28, 2010 at 02:07:56 (CEST), Kip Warner wrote:
>
>> On Wed, 2010-04-28 at 00:32 +0200, Benjamin Drung wrote:
>>>
>>> The best solution would be autodetection of SSE2 on runtime. That can
>>> be
>>> done with a few lines of code.
>>
>> You're right, that can
On 17:07 Tue 27 Apr , Kip Warner wrote:
> On Wed, 2010-04-28 at 00:32 +0200, Benjamin Drung wrote:
> >
> > The best solution would be autodetection of SSE2 on runtime. That can
> > be
> > done with a few lines of code.
>
> You're right, that can indeed be done with a few lines of code. e.g.
Le mardi 27 avril 2010 à 17:07 -0700, Kip Warner a écrit :
> You're right, that can indeed be done with a few lines of code. e.g.
> cpuid instruction. The problem is that you then have to perform a branch
> every time you could potentially use hardware acceleration: a condition
> for when, say, SSE
On Wed, 2010-04-28 at 12:13 +0200, Josselin Mouette wrote:
> The simplest solution is to put the routines in a shared library and
> to
> build two versions of the library. Put the i486 one in /usr/lib and
> the
> SSE2 one in /usr/lib/i686/sse2.
That might be the way to go. Thanks.
--
Kip Warner
15 matches
Mail list logo
