Assembly code with Borland's C compiler

Thanks Chris. I'll follow your suggestion.

Hul

Chris H wrote:

Jim - I'll look at those, thanks.

Hul

Jim Stewart wrote:

doesn't

comp.arch.embedded Assembly code with Borland's C compiler

More working with Borland's compiler: trying to link 2 .obj files generated by Borland's compiler without any errors indicated, untill the .exe is executed. Then windows pops a window saying, roughly, this application has generated an error and we are closing the application - an error log is being created. Anyone know where Microsoft hides their error logs?

Hul

It depends. On some architectures, fetching a few values from parameter registers is a lot easier than constructing a global variable address in an address register and dereferencing that.

The best way is, of course, to use GNU-style asm operand constraints.

Stefan

ed

CPU type is fairly obvious. Not what I meant. Is the OP targeting some kind of DOS like target, bare-metal (Phar Lap like target) or some kind of Win32 based target?

To me it sounds like he may be trying to target something Win32 based and needs to contact the specific vendor. Most people don't mix Microsoft and Borland for DOS or bare metal targets.

generated

eing

Is this an embedded target?

What OS ?

This is an embedded news group.

There are literally hundreds of thousands of embedded DOS computers out there. I know, I built a few tens of thousands of them...

Apart from that the 386 was quite widely used in embedded work. There was a specific embedded version AFAIr. Whilst not as common as some MCU the x86 family was used in embedded work with and without a DOS & BIOS

Where x86 was used for embedded work the Borland compiler tended to be the compiler of choice. I have a rom kit for the Borland compilers if anyone is interested.

The 80186(&8)EA/B/C series were used in embedded applications with the Borland compiler, requiring a very small BSP to furnish BIOS compatibility. Nigel Roles (of York University) did much of the groundwork.