| blob | afeff940c438ee7c036f49c0bda9b1a3131ab314 |
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><li>
31 </li></ul>
32 </li><li>
34 <ul><li>
36 <ul><li>
38 </li><li>
40 </li><li>
42 </li></ul>
43 </li><li>
45 </li><li>
47 </li></ul>
48 </li><li>
50 <ul><li>
52 </li></ul>
53 </li><li>
55 </li><li>
57 </li><li>
59 </li><li>
61 </li></ul>
62 </div>
64 <dl>
66 <dd>
68 <li>The <a href="http://luajit.org/list.html"><span class="ext">»</span> LuaJIT mailing list</a> focuses on topics
69 related to LuaJIT.</li>
70 <li>The <a href="http://wiki.luajit.org/"><span class="ext">»</span> LuaJIT wiki</a> gathers community
71 resources about LuaJIT.</li>
72 <li>News about Lua itself can be found at the
73 <a href="http://www.lua.org/lua-l.html"><span class="ext">»</span> Lua mailing list</a>.
74 The mailing list archives are worth checking out for older postings
75 about LuaJIT.</li>
76 <li>The <a href="http://lua.org"><span class="ext">»</span> main Lua.org site</a> has complete
77 <a href="http://www.lua.org/docs.html"><span class="ext">»</span> documentation</a> of the language
78 and links to books and papers about Lua.</li>
79 <li>The community-managed <a href="http://lua-users.org/wiki/"><span class="ext">»</span> Lua Wiki</a>
80 has information about diverse topics.</li>
81 </ul>
82 </dl>
84 <dl>
86 <dd>
87 I'm planning to write more documentation about the internals of LuaJIT.
88 In the meantime, please use the following Google Scholar searches
89 to find relevant papers:<br>
90 Search for: <a href="http://scholar.google.com/scholar?q=Trace+Compiler"><span class="ext">»</span> Trace Compiler</a><br>
91 Search for: <a href="http://scholar.google.com/scholar?q=JIT+Compiler"><span class="ext">»</span> JIT Compiler</a><br>
92 Search for: <a href="http://scholar.google.com/scholar?q=Dynamic+Language+Optimizations"><span class="ext">»</span> Dynamic Language Optimizations</a><br>
93 Search for: <a href="http://scholar.google.com/scholar?q=SSA+Form"><span class="ext">»</span> SSA Form</a><br>
94 Search for: <a href="http://scholar.google.com/scholar?q=Linear+Scan+Register+Allocation"><span class="ext">»</span> Linear Scan Register Allocation</a><br>
95 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>
96 And, you know, reading the source is of course the only way to enlightenment. :-)
97 </dd>
98 </dl>
100 <dl>
102 Q: My vararg functions fail after switching to LuaJIT!</dt>
106 <a href="http://www.lua.org/manual/5.1/manual.html#2.5.9"><span class="ext">»</span> Lua 5.1
108 </dl>
110 <dl>
114 </dt>
115 <dd>
117 DirectX/Direct3D (up to version 9) sets the x87 FPU to single-precision
118 mode by default. This violates the Windows ABI and interferes with the
119 operation of many programs — LuaJIT is affected, too. Please make
121 initializing Direct3D.<br>
123 Direct3D version 10 or higher do not show this behavior anymore.
124 Consider testing your application with older versions, too.<br>
126 Similarly, the Borland/Delphi runtime modifies the FPU control word and
127 enables FP exceptions. Of course this violates the Windows ABI, too.
128 Please check the Delphi docs for the Set8087CW method.
130 </dl>
132 <dl>
134 <dd>The interrupt signal handler sets a Lua debug hook. But this is
135 currently ignored by compiled code (this will eventually be fixed). If
136 your program is running in a tight loop and never falls back to the
137 interpreter, the debug hook never runs and can't throw the
139 twice to get stop your program. That's similar to when it's stuck
140 running inside a C function under the Lua interpreter.</dd>
141 </dl>
143 <dl>
145 <dd>Because it's a completely redesigned VM and has very little code
146 in common with Lua anymore. Also, if the patch introduces changes to
147 the Lua semantics, these would need to be reflected everywhere in the
148 VM, from the interpreter up to all stages of the compiler.<br> Please
149 use only standard Lua language constructs. For many common needs you
150 can use source transformations or use wrapper or proxy functions.
151 The compiler will happily optimize away such indirections.</dd>
152 </dl>
154 <dl>
157 machine code. This means the code generator must be ported to each
158 architecture. And the fast interpreter is written in assembler and
159 must be ported, too. This is quite an undertaking.<br>
161 architectures. Other architectures will follow based on sufficient user
162 demand and/or sponsoring.</dd>
163 </dl>
165 <dl>
168 C'mon, it's open source — I'm doing it on my own time and you're
169 getting it for free. You can either contribute a patch or sponsor
170 the development of certain features, if they are important to you.
171 </dd>
172 </dl>
174 </div>
179 ·
181 </span>
182 </div>
183 </body>
184 </html>