[sdcc-devel] possible bug?

[<Tre...@sm...>]

This may not be the correct list.  If not, sorry.
I just discovered SDCC and I was checking the
docs to see if it can do what I need.  I discovered
a potential bug, based on what I read.

If you use the "-stack-auto" option (which is highly desireable)
then according to your documention the use of setjmp() and longjmp()
is precluded because these functions ignore _bp.
Perhaps this is handled already and the documentation is just stale?

Sparing you the reasons, I need to put all items in memory at fixed addresses.
This includes compiler generated phaux registers like _bp.
(and anything else generated by the compiler).
_sdcc__external_startup() doesn't cut it.
Is there some "startup.asm" file or such that allows absolute location of _bp etc,
as well as the clearing of sundry memory ranges and variable initialization?
(I can't have the compiler wiping the contents of my nv-memory...)
Where is the source for the boot code?  Did I just miss it?

Sorry if I missed this stuff in a FAQ or something.  I'm scrambling to make
at least one of about 4 commercial compilers do what I need, and
now I've found SDCC, which could possibly rule all, if I can make it do this stuff.

Thanks,
Trenton Henry
Senior Principal Software Engineer
Standard Microsystems Corp.
Austin Design Center