delorie.com/archives/browse.cgi | search |
From: | gpt20 AT thor DOT cam DOT ac DOT uk (G.P. Tootell) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: at&t opcodes -> intel opcodes |
Date: | 21 Jan 1997 09:55:39 GMT |
Organization: | University of Cambridge, England |
Lines: | 13 |
Sender: | gpt20 AT hammer DOT thor DOT cam DOT ac DOT uk (G.P. Tootell) |
Message-ID: | <5c23qr$9l4@lyra.csx.cam.ac.uk> |
References: | <5bvu1i$di AT lyra DOT csx DOT cam DOT ac DOT uk> <19970120 DOT 191505 DOT 4983 DOT 1 DOT chambersb AT juno DOT com> |
NNTP-Posting-Host: | hammer.thor.cam.ac.uk |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
you're right. i'm going mad in my old age :) for some reason i have 3 references here, each gives different cycle timings and the reference i was using didn't seem to list all the floating point instructions for no obvious reason :( nik |> > |> The opcodes are exactly the same. The only difference is with AT&T, the |> source is on the left and the dest on the right. |> |> ..Chambers --
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |