Ian Lance Taylor wrote: > No, that makes no sense. What I'm suggesting is that we fix the stack > offsets of all local variables before register allocation, based on a > conservative assessment of how many registers will be saved on the > stack.
The conservative assessment is that all pseudos go on the stack. However, this way you'll generate terrible code. I don't really understand why people want to remove reload only to implement the same thing elsewhere. There are only two major problems with reload IMO: - the RELOAD_FOR_xxx mechanism of scheduling reload insns is terrible - so is the inheritance code Even so, the number of bugs in these seems to have dropped off over the years. If you replace these two with a cleaner solution, you'll end up with a fairly clean and easy to understand reload pass. We'd still want the register allocator to be strong enough not to leave too much work for it, but I simply don't see how reload can be entirely replaced in gcc. Bernd -- This footer brought to you by insane German lawmakers. Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 40368 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
