> > void op_cfc1 (void) > > { > > +#ifdef __s390__ > > + if(!T1) > > + T0 = (int32_t)env->fcr0; > > I guess this breaks when you _breathe_ at the compiler. Inventing > switch-table support in dyngen would be preferable (if possible...).
Actually, I'm surprised this doesn't break on other hosts. Jump tables are death on all targets, I guess s390 gcc happens to use different heuristics for expanding switch statements. I suspect making dyngen handle jump tables is not going to happen. Paul