<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il Mar 8 Feb 2022, 20:54 Michal Vlasák <<a href="mailto:lahcim8@gmail.com">lahcim8@gmail.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue Feb 8, 2022 at 8:05 AM CET, luigi scarso wrote:<br>
> Can you post a patch using the current luatex experimental repo at<br>
> <a href="https://serveur-svn.lri.fr/svn/modhel/luatex/branches/experimental/" rel="noreferrer noreferrer" target="_blank">https://serveur-svn.lri.fr/svn/modhel/luatex/branches/experimental/</a><br>
> (see <a href="http://www.luatex.org/download.html" rel="noreferrer noreferrer" target="_blank">http://www.luatex.org/download.html</a> ) ?<br>
<br>
Attached.<br>
<br>
I don't know how basing one patch on top of another works with TLpatches<br>
and its .original files. I don't even even know if its manual or not, I<br>
constructed the TLpatch file manually.<br>
<br>
>From the version I shared last time there are three changes:<br>
<br>
- byte swapping when loaded byte code has different byte order<br>
- for simplicity I am wasting 8 bytes in each bytecode for detecting<br>
byte order and actually verify that integers dump correctly<br>
- I changed the "version" byte from 0 to 'T' so that it is explicit<br>
that other Lua 5.3.6 bytecodes are incompatible with LuaTeX<br>
<br>
Neither the variable length encoding, neither byte swapping are compile<br>
time options. I don't really want to get into preprocessor macros. This<br>
seemed the simplest thing to work and shouldn't have much runtime cost<br>
for most runs.<br>
<br>
Just for record, I am not a proponent of these changes, it's a<br>
demonstration that it can and has to be done on the Lua level and that<br>
it seemingly works.<br>
<br>
Also, LuaJIT bytecode is portable across all its architectures AFAIK, so<br>
no problem with LuaJITTeX.<br>
<br>
Sorry, I also didn't test the LuaTeX repository build, it's hard for me<br>
to cross compile and run binaries that excersise byte order issues<br>
and/or 16/32/64 bit architectures problems.<br>
<br>
Michal <br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Ok , thank you very much. </div><div dir="auto">Maybe we can use qemu to check the 32/64 issue ? </div><div dir="auto"><br></div><div dir="auto">--</div><div dir="auto">luigi </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>