From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Unusual effect from DJGPP
Date: 24 Aug 2000 12:37:55 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 17
Message-ID: <8o34v3$d67$1@nets3.rz.RWTH-Aachen.DE>
References: <2000Aug23 DOT 173529 DOT 28049 AT arragonrobots DOT ox DOT ac DOT uk> <vqd8qsg278t4aha9ubu6uubcoc2v17d15h AT 4ax DOT com> <2000Aug24 DOT 121239 DOT 28647 AT arragonrobots DOT ox DOT ac DOT uk>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 967120675 13511 137.226.32.75 (24 Aug 2000 12:37:55 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 24 Aug 2000 12:37:55 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Neil Townsend <neil AT robots DOT ox DOT ac DOT uk> wrote:

> I'm
> currently chasing a suspicion that it's to do with double alignment
> issues (the cpu it works on is a pentium-s, the one it fails on is a
> pentium-mmx, I suspect that these may have differing alignment
> requirements).

x86 CPUs have no alignment requirements that could usually cause the
difference between a crash and no crash. You can get misalignment
penalties in form of some additional CPU cycles, but never a crash.
The only case where this is different is in the context of wraparound
at the end of logical address space, I think.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.