Can you strip down the assembler code to just doing something very basic which uses EAX call it from TC++, get it working, and then add to it gradually?.
And I'm just throwing that out there as an example, I've not seen the code, and I'm not saying this is the issue, just something that jumped out from the TASM manual). ( something like Register Preservation ?.
Like if TASM supports 32bit asm, is the issue within the asm code, or possibly in the integration between TC++ ASM. My general advice is can you can break down your code in smaller chunks and test your assertions in some way. If you're at the point where you need to get inline assembler macros working on a ~30 year old platform what have you got to lose, just grab the latest versions you can find (according to wikipedia 5.x ( link) as I assume you're not using the mobile edition from 2003)) and try and run it on your PC (or preferably in a VM or spare machine) and see what happens.Ĭlick to expand.But I don't want to give you the wrong steer because as said previously I've not used TASM, and I've not touched assembler in *forever*. You'll have to see whether that first option might work for you and with your macros (not sure I've not used it so can't comment). That second option, if you use BASM even though Borland C++ compiler can generate 32bit code, BASM has a 16bit compiler hence you won't get what you're after i.e.: The reason that's significant is EAX is a 32bit register that's only available from the 386 instruction set and above.īorland C++ v5.0 according to the programmers guide - link (pdf) does appear to support 32bit and 16bit compilation, and 2 ways to include inline assembler If your Turbo C++ 3.0 looks like this video at the 3min mark he shows the advanced generation settings:Īnd it only goes up to the 286 instruction set.
0 kommentar(er)
