| blob | f4bc9edd0370223dc61868de1c1bc34df84e4682 |
2 <html>
3 <head>
13 </style>
14 </head>
15 <body>
18 </div>
21 </div>
23 <ul><li>
25 <ul><li>
27 </li><li>
29 </li></ul>
30 </li><li>
32 <ul><li>
34 <ul><li>
36 </li><li>
38 </li><li>
40 </li></ul>
41 </li><li>
43 </li><li>
45 </li></ul>
46 </li><li>
48 <ul><li>
50 </li></ul>
51 </li><li>
53 </li><li>
55 </li><li>
57 </li></ul>
58 </div>
60 <dl>
62 <dd>
64 <li>The <a href="http://lua.org"><span class="ext">»</span> main Lua.org site</a> has complete
65 <a href="http://www.lua.org/docs.html"><span class="ext">»</span> documentation</a> of the language
66 and links to books and papers about Lua.</li>
67 <li>The community-managed <a href="http://lua-users.org/wiki/"><span class="ext">»</span> Lua Wiki</a>
68 has information about diverse topics.</li>
69 <li>The primary source of information for the latest developments surrounding
70 Lua is the <a href="http://www.lua.org/lua-l.html"><span class="ext">»</span> Lua mailing list</a>.
71 You can check out the <a href="http://lua-users.org/lists/lua-l/"><span class="ext">»</span> mailing
72 list archive</a> or
73 <a href="http://bazar2.conectiva.com.br/mailman/listinfo/lua"><span class="ext">»</span> subscribe</a>
74 to the list (you need to be subscribed before posting).<br>
75 This is also the place where announcements and discussions about LuaJIT
76 take place.</li>
77 </ul>
78 </dl>
80 <dl>
82 <dd>
83 I'm planning to write more documentation about the internals of LuaJIT.
84 In the meantime, please use the following Google Scholar searches
85 to find relevant papers:<br>
86 Search for: <a href="http://scholar.google.com/scholar?q=Trace+Compiler"><span class="ext">»</span> Trace Compiler</a><br>
87 Search for: <a href="http://scholar.google.com/scholar?q=JIT+Compiler"><span class="ext">»</span> JIT Compiler</a><br>
88 Search for: <a href="http://scholar.google.com/scholar?q=Dynamic+Language+Optimizations"><span class="ext">»</span> Dynamic Language Optimizations</a><br>
89 Search for: <a href="http://scholar.google.com/scholar?q=SSA+Form"><span class="ext">»</span> SSA Form</a><br>
90 Search for: <a href="http://scholar.google.com/scholar?q=Linear+Scan+Register+Allocation"><span class="ext">»</span> Linear Scan Register Allocation</a><br>
91 Here is a list of the <a href="http://article.gmane.org/gmane.comp.lang.lua.general/58908"><span class="ext">»</span> innovative features in LuaJIT</a>.<br>
92 And, you know, reading the source is of course the only way to enlightenment. :-)
93 </dd>
94 </dl>
96 <dl>
98 Q: My vararg functions fail after switching to LuaJIT!</dt>
102 <a href="http://www.lua.org/manual/5.1/manual.html#2.5.9"><span class="ext">»</span> Lua 5.1
104 </dl>
106 <dl>
110 </dt>
111 <dd>
113 DirectX/Direct3D (up to version 9) sets the x87 FPU to single-precision
114 mode by default. This violates the Windows ABI and interferes with the
115 operation of many programs — LuaJIT is affected, too. Please make
117 initializing Direct3D.<br>
119 Direct3D version 10 or higher do not show this behavior anymore.
120 Consider testing your application with older versions, too.<br>
122 Similarly, the Borland/Delphi runtime modifies the FPU control word and
123 enables FP exceptions. Of course this violates the Windows ABI, too.
124 Please check the Delphi docs for the Set8087CW method.
126 </dl>
128 <dl>
130 <dd>The interrupt signal handler sets a Lua debug hook. But this is
131 currently ignored by compiled code (this will eventually be fixed). If
132 your program is running in a tight loop and never falls back to the
133 interpreter, the debug hook never runs and can't throw the
135 twice to get stop your program. That's similar to when it's stuck
136 running inside a C function under the Lua interpreter.</dd>
137 </dl>
139 <dl>
141 <dd>Because it's a completely redesigned VM and has very little code
142 in common with Lua anymore. Also, if the patch introduces changes to
143 the Lua semantics, these would need to be reflected everywhere in the
144 VM, from the interpreter up to all stages of the compiler.<br> Please
145 use only standard Lua language constructs. For many common needs you
146 can use source transformations or use wrapper or proxy functions.
147 The compiler will happily optimize away such indirections.</dd>
148 </dl>
150 <dl>
153 machine code. This means the code generator must be ported to each
154 architecture. And the fast interpreter is written in assembler and
155 must be ported, too. This is quite an undertaking.<br>
157 architectures. Other architectures will follow based on sufficient user
158 demand and/or sponsoring.</dd>
159 </dl>
161 <dl>
164 C'mon, it's open source — I'm doing it on my own time and you're
165 getting it for free. You can either contribute a patch or sponsor
166 the development of certain features, if they are important to you.
167 </dd>
168 </dl>
170 </div>
175 ·
177 </span>
178 </div>
179 </body>
180 </html>