https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #8 from davem at gcc dot gnu.org ---
I cannot think of any specific reason why the jump tables were put into the
text section. I even tried to consider relocation ramifications.
Maybe this makes GOT OP linker optimizations more likel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
Eric Botcazou changed:
What|Removed |Added
CC||davem at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #6 from Eric Botcazou ---
> So assuming the intend is to put the jump table in the rodata section,
> something seems to be broken in the build then.
No, see my earlier remark, this was intended.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #5 from Jean-Christophe Dubois ---
I guess JUMP_TABLES_IN_TEXT_SECTION is supposed to mean that the "jump tables"
should not be put in the text section.
However something is wrong then because gcc 9 (and maybe previous) is putting
th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #4 from Jean-Christophe Dubois ---
Created attachment 47475
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47475&action=edit
assembly file with jump tables in the text section
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #3 from Eric Botcazou ---
The decision dates back to the rewrite of the SPARC port in 1998:
21652 davem /* Align to cache line in the function's code section. */
21652 davem function_section (current_function_decl);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
