Prev: Assembly code with Borland's C compiler
Next: CC2430 Interrupt and Communication
From: Hul Tytus on 28 Dec 2009 16:54
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


From: Stefan Reuther on 28 Dec 2009 17:40
Vladimir Vassilevsky wrote:
> Chris H wrote:
>> I always recommended that method. Particularly when people wanted in
>> line assembly or a small amount of assembly in a C program.
>>
>> write an empty c function call, with all the parameters, compile to
>> assembler and out the body in by hand.
>
> The simple and stupid way for passing parameters between C and assembler
> is by global variables.

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

From: Marco on 29 Dec 2009 11:37
On Dec 28, 10:19 am, Chris H <ch...(a)phaedsys.org> wrote:
> In message <d6b5e078-9226-4f28-9f2d-db945618a...(a)o28g2000yqh.googlegroup
> s.com>, Marco <prenom_no...(a)yahoo.com> writes
>
> >On Dec 27, 10:23 am, Hul Tytus <h...(a)panix.com> wrote:
> >> comp.arch.embedded
> >> Assembly code with Borland's C compiler
>
> >> Anyone have suggestions regarding the form for assembley code files used
> >> with Borland's version C compiler?
>
> > What embedded target is this for?
>
> X86  AFAIK Borland only did compilers for X86

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.


From: Marco on 29 Dec 2009 11:39
On Dec 28, 2:54 pm, Hul Tytus <h...(a)panix.com> wrote:
> 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

Is this an embedded target?

What OS ?

This is an embedded news group.
From: Jim Stewart on 29 Dec 2009 14:20
Marco wrote:
> On Dec 28, 2:54 pm, Hul Tytus <h...(a)panix.com> wrote:
>> 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
>
> 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...

 |  Next  |  Last
Pages: 1 2
Prev: Assembly code with Borland's C compiler
Next: CC2430 Interrupt and Communication