This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Note that we can still have a single_set which appears inside a PARALLEL (the other expressions will be CLOBBERS, USEs and SETs with an output that is not used).
Now, I think update_equiv_regs only handles two cases. 1. A register used inside one basic block only, set only once, and written to memory, becomes REG_EQUIV to that location. 2. Register always set to the same value which is REG_EQUAL to something else.
Do we need to worry about the case where we have a pseudo equivalenced to a read-only memory location that initially gets a hard register, but later that hard reg is spilled? Do we replace the pseudo with its equivalent memory location in that case? If so, then I think we need some compensation code for that case as well.
As for testcode -- if it passes mainline bootstrap, then you've exercised the testcode.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |