[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] Ramend in the iom103.h file
From: |
Joerg Wunsch |
Subject: |
Re: [avr-gcc-list] Ramend in the iom103.h file |
Date: |
Thu, 5 Sep 2002 11:01:17 +0200 (MET DST) |
Grant Stockly <address@hidden> wrote:
> Could I change this to 0x0FE1 and have the compiler automatically start the
> stack pointer 30 bytes lower? (And at the same time try not to allocate
> ram above 0xFE1?)
Nope. The compiler doesn't care for its include files. ;-)
> I have a large assembly routine that needs a pretty big storage area
> for variables.
So what's the problem? Simply declare the storage to belong to the
.bss section inside the assembler code, and the linker will take care
to arrange for it, together with the other compiler-generated .bss
variables. The startup code will clear that SRAM area to 0.
Alternatively, put it into .data, then you can initialize it to
arbitrary values, but it'll also consume flash (to write down the
initialization values).
--
J"org Wunsch Unix support engineer
address@hidden http://www.interface-systems.de/~j/
avr-gcc-list at http://avr1.org
- [avr-gcc-list] Ramend in the iom103.h file, Grant Stockly, 2002/09/06
- Re: [avr-gcc-list] Ramend in the iom103.h file,
Joerg Wunsch <=
- Re: [avr-gcc-list] Ramend in the iom103.h file, Grant Stockly, 2002/09/06
- [avr-gcc-list] Accessing C sram locations in inline asm, Grant Stockly, 2002/09/06
- Re: [avr-gcc-list] Accessing C sram locations in inline asm, Theodore A. Roth, 2002/09/06
- Re: [avr-gcc-list] Accessing C sram locations in inline asm, Grant Stockly, 2002/09/10
- Re: [avr-gcc-list] Accessing C sram locations in inline asm, Theodore A. Roth, 2002/09/10
- Message not available
- [avr-gcc-list] ASM SRAM test results, Grant Stockly, 2002/09/10
- Re: [avr-gcc-list] Ramend in the iom103.h file, Joerg Wunsch, 2002/09/06