First  |  Prev |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
x86 Assembly Language FAQ - A86 and D86
X-Disclaimer: Approval for *.answers is based on form, not content. Approved: news-answers-request(a)MIT.EDU Followup-To: alt.lang.asm,comp.lang.asm.x86 Organization: Forever Young Software Distribution: world Expires: Thur, 22 Jan 2015 23:59:59 GMT Summary: This is the FAQ for the x86 Assembly Language programmers... 3 Feb 2010 11:40
x86 Assembly Language FAQ - Microsoft MASM
X-Disclaimer: Approval for *.answers is based on form, not content. Approved: news-answers-request(a)MIT.EDU Followup-To: alt.lang.asm,comp.lang.asm.x86 Organization: Forever Young Software Distribution: world Expires: Thur, 22 Jan 2015 23:59:59 GMT Summary: This is the FAQ for the x86 Assembly Language programmers... 3 Feb 2010 11:40
Skybuck Flying learns hex... [was Re: Intel documentation mistake for single floating point precision !]
"Skybuck Flying" <IntoTheFuture(a)hotmail.com> wrote in message news:83bbd$4b683ea9$d53371df$10717(a)cache4.tilbu1.nb.home.nl... "Single precision: 24 bits" What?! You say that's in the floating point section? Ok... 24 bits would mean: 2^24 = 16777216 For an unsigned integer in binary, there are 1677... 2 Feb 2010 21:54
1D to 3D coordinate translation. (No 16 million is right ?!)
Ok I think the ixbtlabs article is wrong after all... (4095 * 4095)-1 seems to work just fine... My project has problem though... I need to be able to multiply 8000*8000... which is apperently way out of range... I might have to do manual multiplication algorithm somehow to make it work... Bye, Sk... 2 Feb 2010 14:25
Intel documentation mistake for single floating point precision ! (Nope oops lol)
Nope, it's not a mistake... I made a mistake... 8000*8000 is way over 24 bits ! ;) :) I checked with this calculator: http://www.h-schmidt.net/FloatApplet/IEEE754.html And also by doing (2^24) ^ 0.5 = 4096 So: (4095 * 4095)-1 is still in range ! ;) Bye, Skybuck =D ... 2 Feb 2010 14:25
Intel documentation mistake for single floating point precision !
Intel document: " The IA-32 Intel Architecture Software Developer's Manual, Volume 1, Basic Architecture, Document Number 253665 rev 19.pdf" Contains a serious mistake on page 4-5: " Table 4-2. Length, Precision, and Range of Floating-Point Data Types " It reads: " Single precision: 24 bits " ... 2 Feb 2010 14:25
1D to 3D coordinate translation. (testing hardware precision for 3d textures and inprecise 3d texture coordinates)
Remaining question is: What does the hardware do when it encounters an inprecise 3D texture coordinate ? For example instead of: 0, 0, 0.265 it encounters: 0, 0, 0.2649999856948853 (53/200 in 32 bit floating point) The hardware "knows" the texture is 500x400x200 If the hardware is inprecise it w... 2 Feb 2010 14:25
Business Analyst Online Training @ CVK OLT starts on Feb, 1st 8:30 PM EST
Objective: A branded program suite to provide knowledge, skill and attitude required for Business Analysts. This suite of program covers all aspects of Business engineering, Requirements elicitation, Requirements verification, Requirements documentation and Requirements tracing. Key Focus Areas: • BA’s ro... 2 Feb 2010 14:25
Optimization Question: Dynamic ByteArray[ Offset Calculation ] vs (Pointer + Offset Calculation)
Hello, I wonder if the following code might produce different results in Delphi: var a : pointer; // pointer to array a b : array of byte; // pointer to array b p : pointer; begin p := pointer( a + offset calculation (multplication involved) ); vs p := @b[ offset calculation (mu... 2 Feb 2010 14:25
use speakers
i find this code in internet i traslate this NBASM assembly to NASM but it seems the timer never end possibily i copy something wrong but what? Is it possible use the timer of keyboard like timer? there is some dx of kind out dx, ax that sleep for ax seconds? thanks ;com file ;nasmw -o m.com m.asm ;... 26 Feb 2010 15:18
First  |  Prev |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21