#173073 - Ruben - Fri Mar 19, 2010 2:55 pm
Hi.
I was working on my small just-for-the-fun-of-it game [using my own linkscripts + cart files]... and I came across a strange problem.
At first, it would link fine but... it would place some of my RAM sections in BSS, even though they were initialized and explicitly declared to be in RAM. However, when I placed some more safeguards [like ALIGN(4) on the VMA] in the linkscript, it came up with...
I'm not 100% sure but... isn't a negative overflow a problem with the linker, rather than my code?
[it was working a few minutes ago, when the size was around 200KB bigger]
I was working on my small just-for-the-fun-of-it game [using my own linkscripts + cart files]... and I came across a strange problem.
At first, it would link fine but... it would place some of my RAM sections in BSS, even though they were initialized and explicitly declared to be in RAM. However, when I placed some more safeguards [like ALIGN(4) on the VMA] in the linkscript, it came up with...
| Code: |
| d:/devkitpro/devkitarm/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld.exe: region `ram' overflowed by -37703456 bytes |
I'm not 100% sure but... isn't a negative overflow a problem with the linker, rather than my code?
[it was working a few minutes ago, when the size was around 200KB bigger]