sgundapa added a comment. The discussion is scattered across these patches https://reviews.llvm.org/D35578 and https://reviews.llvm.org/D35579. I will provide a brief summary here:
The idea is to control the generation of data (lookup table) generated from a function, specifically when the user is not expecting it. For hexagon, there is tightly coupled memory and the customers usually place "text" in it. For functions, which generate lookup tables, it is very very expensive to read the table from a far away non-TCM data section. This option will disable the generation of lookup tables at the expense of code bloat. This is really driven by the customers of hexagon backend. https://reviews.llvm.org/D35577 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
