* Query about reload pass !!
@ 2002-10-18 7:24 Ranjit Singh
2002-10-18 11:35 ` Jim Wilson
0 siblings, 1 reply; 2+ messages in thread
From: Ranjit Singh @ 2002-10-18 7:24 UTC (permalink / raw)
To: gcc
Hi Everyone,
The reload pass has lots of complicated code.
People who have actually worked on it might have
better understanding of it. So I request them to
help me understand some aspects of it.
I am interested to know how exactly replacement of
regs which fail to get hard regs take place.
The array reg_equiv_memory_loc seems to be holding
equivalent stack locations, but where in reload do
we replace them in insn chain.
And does new reg allocator also has similar
processing.
Thanks for your kind help,
Regards,
Ranjit.
__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Query about reload pass !!
2002-10-18 7:24 Query about reload pass !! Ranjit Singh
@ 2002-10-18 11:35 ` Jim Wilson
0 siblings, 0 replies; 2+ messages in thread
From: Jim Wilson @ 2002-10-18 11:35 UTC (permalink / raw)
To: Ranjit Singh; +Cc: gcc
>I am interested to know how exactly replacement of
>regs which fail to get hard regs take place.
Pseudo-regs are unique rtl, so we only have to make one change in order to
modify all uses of a pseudo-reg. This is done in alter_reg to convert
pseudo-regs into hard-regs, and near the end of reload() to convert pseudo
regs into MEMs. Search for regno_reg_rtx.
>And does new reg allocator also has similar
>processing.
I don't know. Probably.
Jim
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-18 16:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-18 7:24 Query about reload pass !! Ranjit Singh
2002-10-18 11:35 ` Jim Wilson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).