The actual tableGen generate a chain of if/then/else for the intrinsic which
is too long for VS 2005, and result in a compile error. I did a small change
in table gen so that the if aren't chained so that I could compile (patch
attached). This double the algorithmic complexity of the function but it
seems that this wasn't a problem. If speed is needed here, we could hash the
string first in a few bin and do the if/then/else in each bin or use a
perfect hash or some hash container.