[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Eric Botcazou changed: What|Removed |Added Assignee|ebotcazou at gcc dot gnu.org |unassigned at gcc dot gnu.org

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Jakub Jelinek changed: What|Removed |Added Target Milestone|8.5 |---

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Jakub Jelinek changed: What|Removed |Added Target Milestone|8.4 |8.5 --- Comment #20 from Jakub Jelinek

[Bug target/92902] jump tables are put into the text section

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

[Bug target/92902] jump tables are put into the text section

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

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Mikael Pettersson changed: What|Removed |Added CC||mikpelinux at gmail dot com --- Comm

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 --- Comment #16 from Andrew Pinski --- (In reply to Jean-Christophe Dubois from comment #15) > Am I missing something? YES. Most likely it will not be loaded in the instruction cache as it is larger than the cache line size.

[Bug target/92902] jump tables are put into the text section

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

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 --- Comment #14 from Richard Henderson --- The only reason I can think for jump tables to be put into the text section is the old aout format, which didn't have a separate read only data section. There should be no reason to do that these days.

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Eric Botcazou changed: What|Removed |Added CC||rth at gcc dot gnu.org --- Comment #13 f

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 --- Comment #12 from davem at gcc dot gnu.org --- I think that case vector stuff was written by Richard Henderson FWIW.

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Eric Botcazou changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 --- Comment #10 from Eric Botcazou --- The SPARC port even has a specific implementation here: /* This is how we hook in and defer the case-vector until the end of the function. */ #define ASM_OUTPUT_ADDR_VEC(LAB,VEC) \ sparc_defer_case_ve

[Bug target/92902] jump tables are put into the text section

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92902 Eric Botcazou changed: What|Removed |Added Summary|jump tables are put in the |jump tables are put into