diff options
Diffstat (limited to 'doc/status.html')
-rw-r--r-- | doc/status.html | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/status.html b/doc/status.html index 2d750ee1..c4d9170f 100644 --- a/doc/status.html +++ b/doc/status.html | |||
@@ -53,10 +53,8 @@ page. | |||
53 | <span style="color: #c00000;">LuaJIT 2.0</span> is the currently active | 53 | <span style="color: #c00000;">LuaJIT 2.0</span> is the currently active |
54 | <span style="color: #c00000;">development branch</span>. | 54 | <span style="color: #c00000;">development branch</span>. |
55 | It has <b>Beta Test</b> status and is still undergoing | 55 | It has <b>Beta Test</b> status and is still undergoing |
56 | substantial changes. It's expected to quickly mature within the next | 56 | substantial changes. It's maturing quickly, so you should definitely |
57 | months. You should definitely start to evaluate it for new projects | 57 | start to evaluate it for new projects right now. |
58 | right now. But deploying it in production environments is not yet | ||
59 | recommended. | ||
60 | </p> | 58 | </p> |
61 | 59 | ||
62 | <h2>Current Status</h2> | 60 | <h2>Current Status</h2> |
@@ -153,6 +151,12 @@ with <b>open upvalues aliasing</b> one of the SSA slots later on (or | |||
153 | vice versa). Bonus points, if you can find a real world test case for | 151 | vice versa). Bonus points, if you can find a real world test case for |
154 | this. | 152 | this. |
155 | </li> | 153 | </li> |
154 | <li> | ||
155 | Currently some <b>out-of-memory</b> errors from <b>on-trace code</b> are not | ||
156 | handled correctly. The error may fall through an on-trace | ||
157 | <tt>pcall</tt> (x86) or it may be passed on to the function set with | ||
158 | <tt>lua_atpanic</tt> (x64). | ||
159 | </li> | ||
156 | </ul> | 160 | </ul> |
157 | </li> | 161 | </li> |
158 | </ul> | 162 | </ul> |
@@ -194,7 +198,7 @@ Nonetheless, it compiles to native code and needs to be adapted to each | |||
194 | architecture. Porting the compiler backend is probably the easier task, | 198 | architecture. Porting the compiler backend is probably the easier task, |
195 | but a key element of its design is the fast interpreter, written in | 199 | but a key element of its design is the fast interpreter, written in |
196 | machine-specific assembler.<br> | 200 | machine-specific assembler.<br> |
197 | A preliminary x64 port is already available, thanks to the | 201 | An x64 port is already available, thanks to the |
198 | <a href="sponsors.html">LuaJIT sponsorship program</a>. | 202 | <a href="sponsors.html">LuaJIT sponsorship program</a>. |
199 | Other ports will follow — companies which are | 203 | Other ports will follow — companies which are |
200 | interested in sponsoring a port to a particular architecture, please | 204 | interested in sponsoring a port to a particular architecture, please |