TASM 5.0 versus BSF

[jff...@my-deja.com]

My knowledge of assembler is fairly limited, but I need to fix a
problem. The C++ program I'm working on passes a long int to an asm
procedure by means of an external variable. The asm proc accesses this
with the BSF instruction, but TASM 5.0 crashes when it tries to
assemble this line of code, with Windows 98 reporting a 32 bit access
error.

extrn fixed ; declared as long int fixed in C++

XXX proc
BSF eax,dword ptr fixed

I also get the following message through the Borland 4.52 IDE:

Transfer xxxxx.asm 88:illegal memory reference

Can anyone tell me if this is a known TASM 5.0 bug. I've tried
declaring fixed as: fixed dw 0, to temporarily clear up the illegal
memory reference, but TASM still crashes.

TIA.

-- Jeff Hill

Sent via Deja.com http://www.deja.com/
Before you buy.

[Frans Morsch]

<jff...@my-deja.com> wrote in message
news:se1t84l...@corp.supernews.com...

This is a known bug. You can get a patch for it at:
http://www.borland.com/borlandcpp/cppcomp/tasmfact.html

Frans Morsch