https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89269
Pharos Team <rtos.pharos at outlook dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #4 from Pharos Team <rtos.pharos at outlook dot com> ---
I continue not to understand your point.
Correct me if I'm wrong, it is GCC that generates the assembly instructions to
read from partition1BssEnd, where it shouldn't.
How can this be a linker problem?
Just to make clear, the address 80c00400 belongs is inside the linker script.
It is the MMU that is initialized to state that address as invalid (and it is
correctly initialized as invalid since this address belongs to another
partition).
