Stack

Please post code in the correct way - the above text is unreadable.

There are many, many thousands of decisions the compiler makes when it generates it's code. However, that is not something you should care about, just as you shouldn't care about the algorithm for controlling the ignition system in your car.

Tou are working at the wrong conceptual level, and it doesn't matter how many questions you ask - and how many answers you receive. There will still be thousands of other issues where the compiler decides what to do, and when.

Please post code in the correct way - the above text is unreadable.

There are many, many thousands of decisions the compiler makes when it generates it's code. However, that is not something you should care about, just as you shouldn't care about the algorithm for controlling the ignition system in your car.

Tou are working at the wrong conceptual level, and it doesn't matter how many questions you ask - and how many answers you receive. There will still be thousands of other issues where the compiler decides what to do, and when.

the code exist in « http://www.keil.com/support/man/docs/c166/c166_noframe.htm"

just I've made a copy of this code.

the compiler don't decides what to do, we use directives and configuration to assisit compiler what to do.

so please, the question is clear, why turn arround??

No, the compiler really do decide what to do. We write source code to inform it what we want solved, and we use directives to give it hints about how to solve it.

If it was you who decided what to do, then you wouldn't need to buy the compiler, since you would not have any need for it. The way you decide what to do, is by writing the program in assembler.

just I've made a copy of this code.

Per Westermark is refering to using the pre tags to post code on the forum.

the compiler don't decides what to do, we use directives and configuration to assisit compiler what to do.

so please, the question is clear, why turn arround??

I understand what your trying to do; give a hint to the compiler to use PUSH (system stack) instead of MOV (user stack). But it's a hint so the compiler can still decide to do otherwise.

Could you answer me/us this: -why- do you want the compiler to use PUSH instead of MOV? I don't see why it's important in the first place.

Is not important if we store registers using push or mov R0, just i'm curious to know why there are two possibility to stores registers in stack. so I think there's an option to check off to tell compiler when using push or mov R0.

thanks for advising me to use pre> to post code, it's the first time that I post in this forum.

There is checkbox in the Options for target/C166

"Save temporary variables on User Stack"
If it is checked, then all registers are placed in User Stack, i.e commands like mov [-R0], Rx are used.
If unchecked, then push/pop commands are used instead.

There is checkbox in the Options for target/C166

Thanks Andrey!

For those people who do not use the IDE :-) it's the SAVESYS and SAVEUSR compiler directive. I completly missed those...

See
http://www.keil.com/support/man/docs/c166/c166_cm_directives.htm

Thanks MOMO, I learned something new because of your post.

--
Joost

yes, finally

thanks for you