[sdcc-devel] [ sdcc-Bugs-1405403 ] _stack_end definition missing for pic16

[SourceForge.net <no...@so...>]

Bugs item #1405403, was opened at 2006-01-14 03:46
Message generated for change (Settings changed) made by vrokas
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1405403&group_id=599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pic16 target
Group: non bugs
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Richard Deeley (rdeeley)
>Assigned to: Vangelis Rokas (vrokas)
Summary: _stack_end definition missing for pic16

Initial Comment:

This problem appears specific to mpic16. Using other
processors (such as z80) appears to work OK.

sdcc -mpic16 a.c

message: using default linker script
"/usr/local/share/gputils/lkr/18f452.lkr"
error: missing definition for symbol "_stack_end",
required by
"/usr/local/bin/../share/sdcc/lib/pic16/crt0i.o"


cat a.c

int test;
void main() {
   test = 0;
}

SDCC :
mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08
2.5.4 #1191 (Jan 13 2006) (UNIX) 



----------------------------------------------------------------------

Comment By: Richard Deeley (rdeeley)
Date: 2006-01-17 22:42

Message:
Logged In: YES 
user_id=634964

Yes, I did see the manual. Spent some time looking for this
specific information as well as a web search for these
keywords. Without success, needless to say. Well, like the
HHGG, I guess I should have found it.

Thanks for the info.




----------------------------------------------------------------------

Comment By: Raphael Neider (tecodev)
Date: 2006-01-17 17:00

Message:
Logged In: YES 
user_id=1115835

This is no bug, its a feature:
The pic16 port allows you to specify the location of your
call-stack via pragmas. Use a line like
#pragma stack 0x300 0xff
to place your stack at [0x300..0x3ff], initial stack pointer
will be 0x3ff, our stack grows downwards.
This specification is required exactly once per project.

And, yes: I should go and implement some default behaviour
to suppress this error... as soon as I get an idea, i do it.
BTW: This is documented behaviour, ever seen the SDCC Manual?

Raphael

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1405403&group_id=599