Read only data sections are intermixed with code sections about amiga-gcc HOT 4 CLOSED

So why that's a "won't fix"? As a less experienced programmer I'm a bit confused and worried that such simple thing as declaring a constant before function may cause crashes in my apps. If it's that hard to fix, how does one protect from such unexpected behavior?

from amiga-gcc.

okay, so we had a discussion on slack about it and @michalsc told me that's dangerous only when not using default startup code. So not a problem for me... for now. ;)

from amiga-gcc.

Maybe a tiny fix, where const and any other read only data (which would normally go into .rodata section in ELF) is stored in HUNK_DATA section instead of HUNK_CODE? If necessary one could enforce variables/structures into code section anyway, using attribute((section()))...

Well, I myself can live with "wontfix", my issue was thought rather towards unexperienced developers who may waste hours trying to figure out why the code crashes without any apparent reason.

from amiga-gcc.

It's a good feature to put const data into the text (code) section, since it allows pcrel addressing.
For the rare cases providing an own startup code you can spend the few bytes to add a bra __entrypoint as first insn.

Tiny effort for folks with own startup.
Way less effort for me.
Good!

from amiga-gcc.