Re: [Sdcc-user] Greetings

[Vangelis R. <vr...@ot...>]

----- Original Message -----=20
From: <mt...@be...>
To: <sdc...@li...>
Subject: [Sdcc-user] Greetings


> I'm new to the list, so please excuse me if this question has already =
been=20
> asked. I am working with the Dec 7th snapshot of sdcc (built from =
source).=20
> I am attempting to build a PIC18F252 target. I'm not sure if all the=20
> support is there yet or not - but I can't seem to get past this =
undefined=20
> symbol errro relating to _stack_end and _stack (below). Is this =
something=20
> I can do today with sdcc?

Sure you can, you can either use the #pragma stack directive:
#pragma stack stack_init_pos [stack_size]

or you can use the gplink stack creation argument -t or --stack

Remember that stack_init_pos is the memory position that stack
begin and ends at stack_size-1. You can omit stack_size and the
compiler will initialize a default stack of 64 bytes.

The folllowing limitations apply in the current stack implementations
that need to be fixed:
    1. stack section should be less than 256 bytes,
    2. stack section should be aligned in 256 blocks, starting from 0x0.
        That is it is valid to have stacks that do not cross the banks =
in data
        memory.

Although all these are documented in the manual, the 'large' stack =
feature
is not fully supported, thats why the above limitations apply.

welcome to the list and good luck,

regards,
Vangelis Rokas