1996-12-16 - Re: ASM vs portable code [WAS: Re: Java DES breaker?]

Header Data

From: “John Poole” <jfpoole@undergrad.math.uwaterloo.ca>
To: “Dale Thorn” <trei@process.com>
Message Hash: c5a15d4e3fe46745085ae1e6926fa39e2be85978563e15d2826c8c9d9d06d4c9
Message ID: <199612160438.XAA11664@mag1.magmacom.com>
Reply To: N/A
UTC Datetime: 1996-12-16 04:38:10 UTC
Raw Date: Sun, 15 Dec 1996 20:38:10 -0800 (PST)

Raw message

From: "John Poole" <jfpoole@undergrad.math.uwaterloo.ca>
Date: Sun, 15 Dec 1996 20:38:10 -0800 (PST)
To: "Dale Thorn" <trei@process.com>
Subject: Re: ASM vs portable code [WAS: Re: Java DES breaker?]
Message-ID: <199612160438.XAA11664@mag1.magmacom.com>
MIME-Version: 1.0
Content-Type: text/plain


Dale Thorn wrote:
> I remember sitting down with some ASM programmers in the mid 1980's
> (using x86 PCs), and at that time, looking at the Codeview tracings,
> it occurred to me that ASM would nearly always run 2x faster than 'C',
> something that is inherent in the processes.

This discussion sounds similar to the "C vs. Assembler" thread that's been
raging on comp.lang.c for the past couple of months. The general consensus
seems to be that on an x86 processor, using C for most of your program and
using assembler sparingly is the best way to go. Plus, most compilers will
produce code that runs about 1.2 - 1.5 times slower than your average
assembler code. You mileage, of course, will vary.

-----------------------------------------------
John Poole, 2A AM/CS, University of Waterloo
http://www.undergrad.math.uwaterloo.ca/~jfpoole
"I've gone too far, for too little."






Thread