Re: MMX/3Dnow!/SSE/SSE2 compilers

Andrew Richards <>
23 Apr 2002 23:44:00 -0400

          From comp.compilers

Related articles
MMX/3Dnow!/SSE/SSE2 compilers (Curtis and Disa) (2002-04-21)
Re: MMX/3Dnow!/SSE/SSE2 compilers (Andrew Richards) (2002-04-23)
Re: MMX/3Dnow!/SSE/SSE2 compilers (Andrew Richards) (2002-04-24)
Re: MMX/3Dnow!/SSE/SSE2 compilers (Allan Sandfeld Jensen) (2002-04-24)
Re: MMX/3Dnow!/SSE/SSE2 compilers (2002-04-29)
Re: MMX/3Dnow!/SSE/SSE2 compilers (2002-04-29)
Re: MMX/3Dnow!/SSE/SSE2 compilers (jacob navia) (2002-05-01)
Re: MMX/3Dnow!/SSE/SSE2 compilers (Andrew Richards) (2002-05-01)
[8 later articles]
| List of all articles for this month |

From: Andrew Richards <>
Newsgroups: comp.compilers
Date: 23 Apr 2002 23:44:00 -0400
Organization: blueyonder (post doesn't reflect views of blueyonder)
References: 02-04-126
Keywords: optimize, architecture, comment
Posted-Date: 23 Apr 2002 23:44:00 EDT


Curtis and Disa wrote:
> What compilers support any of the MMX/3Dnow!/SSE/SSE2 instruction sets
> (and optimize code for them)? Do you know of any published
> comparisons of such compilers?

Ours do! :-) We have some comparisons, but they are mainly based on
image and sound processing. We sell to game developers, mostly.

Don't expect these instruction sets to give a significant speed
improvement on standard benchmarks - all the instructions are quite
specifically designed for media processing, where speed improvements
go up to a factor of 4 (and we have found some people have got very
large performance improvements on some software, around 20% is more

Intel also do a compiler which does well on scientific code.

Quite a few other compilers support intrinsics for MMX/3DNow etc., but
that requires writing non-portable code for specific processors.

> - Eythor

Andrew Richards

Tel: +44 (0)20 7482 3382
140-142 Kentish Town Rd, London, NW1 9QB
[I was under the impression that people usually use these vectorish
instructions via libraries more than via in-line code. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.