Open noahgibbs opened 5 years ago
Noah, thank you for reporting this. I'll investigate this problem. Unfortunately, I am busy with GCC-9 release work for now. So I'll do this only after the GCC release (probably at the end of April).
Very reasonable. I just didn't want it to surprise you when I wrote that I couldn't use JIT for evaluating the RTL stuff in an upcoming blog post.
RRB is a pretty heavy usage test and I don't think you need to prioritize this.
The RTL branch ran RRB just fine without JIT, at basically the same speed as release Ruby 2.6. But it crashed rapidly when run with --jit. Here's the stack traces I got when it did:
Release Ruby 2.6 didn't get these errors on the same EC2 instance.