------- Comment #12 from jakub at gcc dot gnu dot org 2009-04-22 17:51 ------- That's not going to fly very well e.g. on ia64: config/ia64/ia64.h:#define FIRST_PSEUDO_REGISTER 334 then we have automatic arrays like: char operands_match[MAX_RECOG_OPERANDS][MAX_RECOG_OPERANDS]; etc., many of them are cleared quite often, so such a change could sometimes lead to overflowing stack and definitely to a noticeable slowdown. Or struct recog_data contains many MAX_RECOG_OPERANDS sized arrays in it. Or e.g.: extern struct operand_alternative recog_op_alt[MAX_RECOG_OPERANDS][MAX_RECOG_ALTERNATIVES]; where operand_alternative struct is pretty large. Many functions also iterate from 0 to MAX_RECOG_OPERANDS.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39847
