https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #19 from Jean-Christophe Dubois ---
(In reply to Andrew Pinski from comment #16)
> (In reply to Jean-Christophe Dubois from comment #15)
> > Am I missing something?
>
> YES. Most likely it will not be loaded in the instruction cach
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #18 from Jean-Christophe Dubois ---
(In reply to Mikael Pettersson from comment #17)
> My though reading this is that most RICSs have problems synthesizing large
> literals, so putting a jump table in .text might increase the likeliho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902
--- Comment #15 from Jean-Christophe Dubois ---
Thanks for the feedback and the support.
Now maybe this is not the good place to ask question but I am wondering:
Most of today's processors have separate data and instruction cache. Isn't it
sub
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
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at tribudubois dot net
Target Milestone: ---
gcc 9.2 (and maybe other versions) is putting jump table directly in the text
section.
On most processors I guess this is not an issue as the text section is usuall
