Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.compilers    |    Compiler construction, theory, etc. (Mod    |    2,753 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,109 of 2,753    |
|    shafi to All    |
|    Re: Pitfalls in interference graph ?    |
|    15 Oct 07 11:46:06    |
      From: shafitvm@gmail.com              > > Now for building the interference graph what other than register pairs       > > is there any other issues that one has to look out for?       >       > - Calling conventions, i.e., caller-saves versus callee-saves       > registers, parameter-transfer registers and registers used for       > return address and stack/frame pointer.       >        parameter-transfer registers,return address registers and       stack/frame registers and other instruction specific and fixed-       function specific registers are handled by perpending and appending       move instructions to the register usages.       For caller/callee saved registers : A call instruction must cause all       volatile (caller-saves) registers to       interfere will all virtual register live at the call point.       Is there anything else other than this ?              Any help would be appreciated.              Regards,       Shafi.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca