<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jun 6, 2015 at 10:38 AM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 06-06-2015, at 10:18 AM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
> Ha! Turns out that at least for sends we're in the clear for out-of-line literal load. i.e. from <a href="https://www.raspberrypi.org/forums/viewtopic.php?f=72&t=78090" target="_blank">https://www.raspberrypi.org/forums/viewtopic.php?f=72&t=78090</a><br>
<br>
</span>Excellent. So the only ‘fun’ is creating, managing and accessing the pools of out of line constants. Where should we place the pool though? My first thought was just in front of the ‘entry’ address but that would screw the assorted entry/nocheck offsets we have as constants. At the end, just before the metadata?<br></blockquote><div><br></div><div>The idea is to dump them somewhere inconspicuours. The natural place is at the head of an else block, i.e. after an unconditional forward branch, or immediately following a return. Here's Object>>printOn: as an example:</div><div><br></div><div>41 <70> self</div><div>42 <C7> send: class</div><div>43 <D0> send: name</div><div>44 <69> popIntoTemp: 1</div><div>45 <10> pushTemp: 0</div><div>46 <88> dup</div><div>47 <11> pushTemp: 1</div><div>48 <D5> send: first</div><div>49 <D4> send: isVowel</div><div>50 <99> jumpFalse: 53</div><div>51 <23> pushConstant: 'an '</div><div>52 <90> jumpTo: 54</div><div><br></div><div>**put literals here**</div><div><br></div><div>53 <22> pushConstant: 'a '</div><div>54 <E1> send: nextPutAll:</div><div>55 <87> pop</div><div>56 <11> pushTemp: 1</div><div>57 <E1> send: nextPutAll:</div><div>58 <87> pop</div><div>59 <78> returnSelf</div><div><br></div><div>**and put literals here**</div><div><br></div><div>The pushConstant: 'a ' at 53 is only reached from the jump at 50. So dumping literals after the jump at 52 is good, as is after the final return.</div><div><br></div><div>However, if code is jump-less and return-less and refers to lots of literals a jump past a run of literals can be inserted as an emergency measure.</div><div><br></div></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>