lsl-luau discrepancy with mono: register exhaustion with concatenation & possible performance issue of list string casting

未关闭
#112 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@HaroldCindy 已经在做这个了。

开始于 2026年11月4日。

评估

这个 Issue 还没有评估数据。

描述

While trying to stress test / benchmark a comparison for (string) list and llDumpList2String, I came across a register exhaustion for a script in lsl-luau that works in mono.

I'm reporting both as one canny because I'm unsure if these are related.

A) First, for the benchmark:

In LSO:


=== list-to-string benchmark: 100 iterations x 300 items ===

(string)list       total = 1040.432007 ms   mean = 10.404320 ms

llDumpList2String  total = 1896.921143 ms   mean = 18.969212 ms

ratio (string/dump) = 0.548485x

=== DONE ===

In Mono:


=== list-to-string benchmark: 100 iterations x 300 items ===

(string)list       total = 226.023000 ms   mean = 2.260230 ms

llDumpList2String  total = 316.186000 ms   mean = 3.161860 ms

ratio (string/dump) = 0.714842x

=== DONE ===

In LSL-LUAU:


=== list-to-string benchmark: 100 iterations x 300 items ===

(string)list       total = 2287.902000 ms   mean = 22.879020 ms

llDumpList2String  total = 589.087000 ms   mean = 5.890871 ms

ratio (string/dump) = 3.883810x

=== DONE ===

===  list-to-string benchmark: 100 reps x 500 items ===

(string)list       total = 4536.675000 ms   mean = 45.366750 ms

llDumpList2String  total = 1022.474000 ms   mean = 10.224740 ms

ratio (string/dump) = 4.436957x

=== DONE ===

Something about how casting a list to a string is way worse in lsl-luau. My thought was that it's likely something that could be optimized if llDumpList2String is about 4x faster already.

B) Second, a test script of the discrepancy is the following


default

{

    state_entry()

    {

        integer i = 1;

        string s =

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i +

            (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i + (string)i ;

        llOwnerSay(s);

    }

}

It prints "1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111" in mono, but in lsl-luau it fails to compile with "Out of registers when trying to allocate 1 registers: exceeded limit 255"

I doubt there are many real use cases where this would have an impact after switching off mono, but it is still a notable difference.

https://secondlife.canny.io/admin/feedback/slua-alpha/p/lsl-luau-discrepancy-with-mono-register-exhaustion-with-concatenation-possible-p

主要语言
C++
星标
25
派生
14
平均合并
1 天 4 小时
30 天内合并 PR
3

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

secondlife/slua 的其他 Issue

查看 secondlife/slua 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。