| ??? 08/17/06 12:04 Read: times |
#122429 - not really Responding to: ???'s previous message |
I still believe it is better if you know where is your assembler and assembler variables when you do mixing.
not really, I have seen some legacy applications of the above that result in HUGE 'holes' in the DATA storage because the linker allocate data per 'module' not per byte. Some absolute locations 'somewhere' can really upset the allocation. What I have done, on occasion, is to have all XDATA in an assembler module and externs in the C. This serves no purpose whatsoever EXCEPT it is so darn nice to debug when a 400h buffer start on a 'page' boundary' My attitude towards 'locating' variables is that either you do them all (all XDATA and/or all DATA) or none. Erik |
| Topic | Author | Date |
| calling c function from assembly | 01/01/70 00:00 | |
| More reading required | 01/01/70 00:00 | |
| AsmCallC | 01/01/70 00:00 | |
| Absolute addresses?? | 01/01/70 00:00 | |
| legacy | 01/01/70 00:00 | |
| not really | 01/01/70 00:00 | |
| NOREGPARAMS | 01/01/70 00:00 | |
| Keil example | 01/01/70 00:00 | |
| undefined varibales | 01/01/70 00:00 | |
| Wouldnt it be easier... | 01/01/70 00:00 | |
| Eh??? | 01/01/70 00:00 | |
| inline | 01/01/70 00:00 | |
what I do and recommend | 01/01/70 00:00 |