search for: reg18888

...eliminated to copies, but this misses the point of my question. What I am asking, is how does stack know that the value of the variable which the resulting value of the phi is currently allocated at. For instance take the instruction: Machine Basic Block (mbb) 12 reg16666 = phi reg17777 (mbb 10), reg18888 (mbb 11). Let reg17777 memory location be at the sp+x, and let reg18888 memory location be at sp+y. What memory location will reg16666 be pointing at? And who tells the stack that it needs to somehow make sure that reg16666 contains the value of 17777 when machine basic block 10 branches to 12? M...

...es the point of my question. > > What I am asking, is how does stack know that the value of the > variable which the resulting value of the phi is currently allocated > at. For instance take the instruction: > > Machine Basic Block (mbb) 12 > reg16666 = phi reg17777 (mbb 10), reg18888 (mbb 11). > > Let reg17777 memory location be at the sp+x, and let reg18888 memory > location be at sp+y. What memory location will reg16666 be pointing > at? And who tells the stack that it needs to somehow make sure that > reg16666 contains the value of 17777 when machine basic bl...

...n. >> >> What I am asking, is how does stack know that the value of the >> variable which the resulting value of the phi is currently allocated >> at. For instance take the instruction: >> >> Machine Basic Block (mbb) 12 >> reg16666 = phi reg17777 (mbb 10), reg18888 (mbb 11). >> >> Let reg17777 memory location be at the sp+x, and let reg18888 memory >> location be at sp+y. What memory location will reg16666 be pointing >> at? And who tells the stack that it needs to somehow make sure that >> reg16666 contains the value of 17777 wh...

...What I am asking, is how does stack know that the value of the >>> variable which the resulting value of the phi is currently allocated >>> at. For instance take the instruction: >>> >>> Machine Basic Block (mbb) 12 >>> reg16666 = phi reg17777 (mbb 10), reg18888 (mbb 11). >>> >>> Let reg17777 memory location be at the sp+x, and let reg18888 memory >>> location be at sp+y. What memory location will reg16666 be pointing >>> at? And who tells the stack that it needs to somehow make sure that >>> reg16666 contains...

At the moment, phi elimination happens before register allocation, so there can be no phis between memory locations. Cameron On Oct 5, 2010, at 4:19 PM, Jeff Kunkel wrote: > When doing phi elimination, does one have to communicate with the > stack space at all? The problem I see is two distinctly different > registers may have two distinctly different stack spaces. When these >

When doing phi elimination, does one have to communicate with the stack space at all? The problem I see is two distinctly different registers may have two distinctly different stack spaces. When these registers are combined in a phi, the values the registers point to needs to be moved, combined, or otherwise taken care of. I understand this is the job of the stack space colorer, but when doing phi