Date: Sat, 16 Nov 1996 15:29:52 -0500
Message-Id: <9611162029.AA18342@robbie.rentec.com>
From: Morten Welinder <welinder AT rentec DOT com>
To: djgpp-workers AT delorie DOT com
Subject: djverify and cpu detection


1. The asm ("...") code in diagnose.c fails to specify that
   ebx/ecx/edx get destroyed.  Bad code may be generated.

2. Why does it .byte and .long so often?  (And what are all
   those '\r's doing _after_ the '\n's?)

3. The method used -- as used everywhere else in djgpp --
   may have a problem: it is said that an interrupt (the
   event, not the handler) will clear the AC flag.

   If this is true then we will occasionally detect 486s
   and up as 386s.

   So someone with a PC should run the cpu detection code
   10^8 times and see if it is reliable.  Don't forget to
   run it in real mode as well as v86 mode.  If it turns
   out we do have a problem we can think of a solution then.

Morten