VOGONS

Common searches


Search results

Display options

Re: AMD64/x86_64 Solution

I'm refering to Memory Addressing. If I allocate a 5 byte block on my computer, i get a pointer to 001. And the machine allocates: 001 <- pointer here. 002 003 004 005 I thought there were some systems that work the other way: 005 <- pointer here 004 003 002 001 so pointer[4] would return 001 Then …

Re: AMD64/x86_64 Solution

Bits compareCount1 = (int)cpos - (int)shortName; Only Works if the high bits that get truncated from the type cast are the same. Bits compareCount1 = (int)(cpos - shortName); This is a better solution, but not the best. If the size difference of the two pointers is greater than the size of an int, …

Re: AMD64/x86_64 Solution

Intresting article. I'm not much a fan of Windows ( and its API ) and therefore don't care much, but It looks like Windows API is going to be really really screwed up when it comes to 64-Bit. I think they should go back to 2-bits and work their way up from there. Looking at the msdn libary and __ …

Re: AMD64/x86_64 Solution

int == 64 and long == 32 on windows? That doesnt sound right. Why would a int be larger than a long int? Windows API calles for Double words instead of long. I've have not seen windows 64 bit version yet. Do they change the API to something else ( DOUBLE DOUBLE WORD? ) or do they just call a 64 bit …

Re: AMD64/x86_64 Solution

It was SEG Faulting with the typical SDL parachute thing. Windows XP would not be affected by this problem because windows does not use 64 bit. This only would occur with Linux compiling as 64 bit. As for the performance, I did not notice any kinds of slow down. But I have not played with it for a …

AMD64/x86_64 Solution

I was having trouble running DOSBox 0.61 on my GNU Linux x86_64 ( custom built distribution). I did some gdb-ing and found it was SEG Faulting in /src/gui/render_templates.h line 13: "case 32:*(Bit32u*)dst=val;dst+=4;break;" Problem is Bit32u is not 32 bits. Therefore adding 4 is wrong. (maybe …

Page 1 of 1