Kenneth Zadeck <[EMAIL PROTECTED]> writes: > There appears to be an idiom, (or at least a chunk of code that has been > heavily copied) where *_output_mi_thunk sets reload_completed and > no_new_pseudos at the top and clears them at the bottom. > > This appears to be the majority of the not trivial places to change and > an explanation by a trained professional would be helpful and greatly > appreciated.
Several of the output_mi_thunk routines essentially run a mini-compilation of a small function. They generate a series of insns, then call final(). Setting reload_completed directs the move expanders to make the right decisions in this limited case. If you remove no_new_pseudos elsewhere in the compiler, you can remove the setting and clearing of no_new_pseudos from *_output_mi_thunk without fear. Ian
