Re: [PATCH 3/8] Speed up constraint_satisfied_p

2014-06-10 Thread Jeff Law
On 06/05/14 15:30, Richard Sandiford wrote: After the earlier changes, the only important function that switches on constraint_num is constraint_satisfied_p (now constraint_satisfied_p_1). Since constraint_num is a dense enum, it seems faster to use a jump table instead. In many cases this allow

[PATCH 3/8] Speed up constraint_satisfied_p

2014-06-05 Thread Richard Sandiford
After the earlier changes, the only important function that switches on constraint_num is constraint_satisfied_p (now constraint_satisfied_p_1). Since constraint_num is a dense enum, it seems faster to use a jump table instead. In many cases this allows the handling function to be a simple sibcall