On 9/9/11 21:41, "Mario" wrote:
>
>The compiler can itself fix the scenarios to make the variables appear in
>such address when needed.
>If the compiler cannot do that, it should at least let me know that that
>rule within a local function
>context, makes no sense.
>
Well, my point was that as co
On Tue, 30 Aug 2011 12:07:29 +0300
Kustaa Nyholm wrote:
> On 8/30/11 01:23, "Mario" wrote:
>
> >Just as described at section 3.6.
> >I have managed to make it work partially, for example, I can decide
> >the address in the RAM of variables only when they are globally
> >defined.
>
> How could
Hi,
c18 uses #pragma to define the section for the following code.
Do we have __attribute__(section) or something like that in SDCC?
If you can control the section for a function, you can play with the gplink
linker script to place any "single function section" anywhere you want.
Sebastien
Le 3
On 8/30/11 01:23, "Mario" wrote:
>Just as described at section 3.6.
>I have managed to make it work partially, for example, I can decide
>the address in the RAM of variables only when they are globally
>defined.
How could you define the address of a local variable? Conceptually
it is in the stac
Hi Mario,
It will put the segment code of file.c at the address 0x7ff0.
On Tue, Aug 30, 2011 at 1:50 AM, Mario wrote:
> Hey Zafi, What of my issues should that suggestion address?
>
> On Mon, Aug 29, 2011 at 8:23 PM, Zafi Ramarosandratana
> wrote:
>> Hi,
>>
>> You may try the following:
>> to c
Hey Zafi, What of my issues should that suggestion address?
On Mon, Aug 29, 2011 at 8:23 PM, Zafi Ramarosandratana
wrote:
> Hi,
>
> You may try the following:
> to compile
> sdcc --codeseg SEGNAME -c file.c
> and to link
> sdcc -Wl -bSEGNAME=0x7ff0 ...
>
> HTH,
> Zafi.
>
> On Tue, Aug 30, 2011
Hi,
You may try the following:
to compile
sdcc --codeseg SEGNAME -c file.c
and to link
sdcc -Wl -bSEGNAME=0x7ff0 ...
HTH,
Zafi.
On Tue, Aug 30, 2011 at 12:23 AM, Mario wrote:
> Just as described at section 3.6.
> I have managed to make it work partially, for example, I can decide
> the addr
Just as described at section 3.6.
I have managed to make it work partially, for example, I can decide
the address in the RAM of variables only when they are globally
defined. But I had to find out about this by myself, because the
manual did not mention this.
The way I had to do it:
unsigned c
On 8/29/11 00:00, "Mario" wrote:
>Is this a currently working feature? can someone provide me some piece
>of code where absolute addressing actually works?
I'm not sure what you re talking about with 'absolute addressing',
please show some code...
br Kusti
-
I have been working for a while on porting my works for CC5X compiler
to SDCC. But I have found a number of problems that I just cannot
manage to resolve and I think the manual lacks a lot of clear
information on how to do some things.
In this one I want to ask about the Absolute Addressing featur
Dear all,
Would it be possible to modify the compiler behaviour to what Cashe
proposed?
I would also expect that the following:
__xdata __at 0x2000 int int_1, int_2;
generates int at 2000 and the next at 2002.
Alex
> Hi all,
> The chapter 3.5 of sdcc manual describes how to assign an absolu
Hi all,
The chapter 3.5 of sdcc manual describes how to assign an absolute address to
variable, but says nothing about what happens when you try to define more
than one member in one statement:
__xdata __at 0x2000 int int_1, int_2;
Maybe it's a good idea to clarify the compiler's behaviour in thi
12 matches
Mail list logo
