linker directive for memory size

OK, so maybe the objdump format isn't so bad, but the mapfile is clearer for some things.

>You might need the "-Wl,xxx" in the IDE.

Because the syntax is so bizarre I list it here:

-Wl,-Map -Wl,'./my_mapfile' ;for just a mapfile

-Wl,-defsym -Wl,'__alt_stack_pointer=0x900000' ;to override stack pointer

-Wl,-defsym -Wl,'__alt_stack_pointer=0x900000',-Map -Wl,'./my_mapfile' ;both

The above are entered as linker flags in the IDE.

Overriding the stack pointer isn't the whole story if you look at the mapfile. The symbol __alt_data_end also extends to the end of memory, and I don't think I want that. Part of the reason is I have less physical memory loaded on my board than is defined in the Nios project (for expandability), but my system worked because the non-functional high order address bit aliased the stack down to a working memory range (whew!). I want the memory limits to be more clearly defined. I also wonder if the stack limits check will work properly.

You cannot use the -defsym trick on __alt_data_end, but if I edit the default linker script to override __alt_data_end instead, the stack pointer gets taken care of automatically. There is a comment which warns against this, but it may be the only way to really get what I want.

thanks