4 Commits

Author	SHA1	Message	Date
Evandro Menezes	eb97e3554c	Add option to specify minimum number of entries for jump tables ... Add an option to allow easier experimentation by target maintainers with the minimum number of entries to create jump tables. Also clarify the name of the other existing option governing the creation of jump tables. Differential revision: https://reviews.llvm.org/D25883 llvm-svn: 285104	2016-10-25 19:53:51 +00:00
Evandro Menezes	601f4cb9f7	Switch lowering: improve partitioning of jump tables ... When there's a tie between partitionings of jump tables, consider also cases that result in no jump tables, but in one or a few cases. The motivation is that many contemporary processors typically perform case switches fairly quickly. Differential revision: https://reviews.llvm.org/D25212 llvm-svn: 285099	2016-10-25 19:11:43 +00:00
Evandro Menezes	055767d5f4	[AArch64] Fix test triplet ... Specify proper target triplet to pass under Windows too. llvm-svn: 282423	2016-09-26 18:09:21 +00:00
Evandro Menezes	e45de8a5ec	Add support to optionally limit the size of jump tables. ... Many high-performance processors have a dedicated branch predictor for indirect branches, commonly used with jump tables. As sophisticated as such branch predictors are, they tend to have well defined limits beyond which their effectiveness is hampered or even nullified. One such limit is the number of possible destinations for a given indirect branches that such branch predictors can handle. This patch considers a limit that a target may set to the number of destination addresses in a jump table. Patch by: Evandro Menezes <e.menezes@samsung.com>, Aditya Kumar <aditya.k7@samsung.com>, Sebastian Pop <s.pop@samsung.com>. Differential revision: https://reviews.llvm.org/D21940 llvm-svn: 282412	2016-09-26 15:32:33 +00:00