At http://gcc.gnu.org/projects/#the_old_problems_file we have a short list coming from the GCC 2 PROBLEMS file. Instead of carrying this around forever, I am wondering whether we could quickly review these and either remove (as not applicable any longer) or move to Bugzilla?
<li value="110">Possible special combination pattern: If the two operands to a comparison die there and both come from insns that are identical except for replacing one operand with the other, throw away those insns. Ok if insns being discarded are known 1 to 1. An andl #1 after a seq is 1 to 1, but how should compiler know that?</li> <li value="117">Any number of slow zero-extensions in one loop, that have their clr insns moved out of the loop, can share one register if their original life spans are disjoint. But it may be hard to be sure of this since the life span data that regscan produces may be hard to interpret validly or may be incorrect after cse.</li> <li value="118">In cse, when a bfext insn refers to a register, if the field corresponds to a halfword or a byte and the register is equivalent to a memory location, it would be possible to detect this and replace it with a simple memory reference.</li> I'll be glad to take care of it, provided guidance from subject matter experts what to do about these three. Gerald
