Mercurial > hg > Papers > 2015 > kaito-lola
changeset 21:a6b9e8b67857
fixxxxx
author | Kaito Tokumori <e105711@ie.u-ryukyu.ac.jp> |
---|---|
date | Sun, 05 Jul 2015 01:27:54 +0900 |
parents | bce15480c8cb |
children | 26e2376219e0 |
files | presentation/presen.html |
diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/presentation/presen.html Sun Jul 05 01:09:28 2015 +0900 +++ b/presentation/presen.html Sun Jul 05 01:27:54 2015 +0900 @@ -269,7 +269,7 @@ <li>Intermediate Representation (bit code). <li>Three forms: in-memory IR, bitcode stream, human readable language. <li>it has precise type, data size, alignment - <li>function call flags : tail, fastcc, cc10, cc11, Erlang, ghc + <li>function call flags : tail, fastcc, cc10(GHC), cc11(HiPE), ccc </ul> <table width='100%'> <tr> @@ -392,7 +392,7 @@ <h2>Tail Call Elimination requirements</h2> <ul> <li>Set tail flag at the code segments call. - <li>Tailcallopt path is enabled in the compiler. + <li>Tail call elimination path is enabled in the compiler. <li>The caller and callee's calling conventions must be the same and their types should be cc10, cc11 or fastcc. <li>Return value type has to be the same as the caller's. </ul> @@ -406,7 +406,7 @@ <li>Fast cc is used consistently in code segments call. <li>All the code segments return value type is void. </ul> - <p>This is the reason why we need __code type for code segments.</p> + <p>These are the reason why we need __code type for code segments.</p> </div> <div class='slide'> @@ -530,7 +530,7 @@ <p>CbC can be used as a hardware description language (RTL level)</p> <ul> <li>VU (Vector unit) in PS2 - <li>SPU in PS3 + <li>SPU (Sound Processing Unit) in PS3 </ul> </div>