Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Reinhard Kotucha
On 2021-07-21 at 15:57:00 +0200, Hans Hagen wrote: > the sharing made sense in the time when one ran tex from a dvd in > which case all binaries shared the same precooked formats (or on > networkshares servingb multiple architectures) but afaik running > from dvd was dropped and hardly anyone

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Hans Hagen
On 7/21/2021 4:08 PM, Michal Vlasák wrote: On Wed Jul 21, 2021 at 3:57 PM CEST, Hans Hagen wrote: even if one would handle bytes in the lua bytecode, the bytecode itself is not portable (and i'm not even sure how luajit stuff fits in because luajit is even more platform specific LuaJIT is actu

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Michal Vlasák
On Wed Jul 21, 2021 at 3:13 PM CEST, Petr Olsak wrote: > IMHO, the TeX engine can save a flag about Endianity to the format. > When a TeX engine reads such a format then it can check the current > Endianity with the saved one and do swapping only if they are > different. But this idea was'nt implem

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Michal Vlasák
On Wed Jul 21, 2021 at 3:57 PM CEST, Hans Hagen wrote: > even if one would handle bytes in the lua bytecode, the bytecode itself > is not portable (and i'm not even sure how luajit stuff fits in because > luajit is even more platform specific LuaJIT is actually really nice in this regard: "Th

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Hans Hagen
On 7/21/2021 3:13 PM, Petr Olsak wrote: Hello, IMHO, the TeX engine can save a flag about Endianity to the format. When a TeX engine reads such a format then it can check the current Endianity with the saved one and do swapping only if they are different. But this idea was'nt implemented: all

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Hans Hagen
On 7/21/2021 1:58 PM, Michal Vlasák wrote: On Wed Jul 21, 2021 at 9:09 AM CEST, Hans Hagen wrote: just afew remarks: - dump sharing in luatex makes no sense, also because lua byte code can be stored and that is not portable .. for that reason byte swapping was removed at some later point in the

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Petr Olsak
Hello, IMHO, the TeX engine can save a flag about Endianity to the format. When a TeX engine reads such a format then it can check the current Endianity with the saved one and do swapping only if they are different. But this idea was'nt implemented: all formats use non-Intel Endianity (by dec

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Michal Vlasák
On Wed Jul 21, 2021 at 9:09 AM CEST, Hans Hagen wrote: > just afew remarks: > > - dump sharing in luatex makes no sense, also because lua byte code > can be stored and that is not portable .. for that reason byte > swapping was removed at some later point in the project Funnily enough, I looked at

Re: [Dev-luatex] Dump sharing - redundant copying/allocations

2021-07-21 Thread Hans Hagen
On 7/20/2021 9:51 PM, Michal Vlasák wrote: On Tue Jul 20, 2021 at 7:56 PM CEST, Taco Hoekwater wrote: Hi, On 20 Jul 2021, at 18:01, Michal Vlasák wrote: Hello, when NO_DUMP_SHARE is not defined and the system is Little endian, then for the possibility of sharing format files between archite