From: "naruse (Yui NARUSE) via ruby-core" Date: 2023-03-08T03:01:06+00:00 Subject: [ruby-core:112727] [Ruby master Bug#19444] YJIT String#+@ miscompilations Issue #19444 has been updated by naruse (Yui NARUSE). Backport changed from 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: REQUIRED to 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONE ruby_3_2 4d75035e1762a23d38c5192b30bb47f40b752bee merged revision(s) c178926fbe879045fa711444a1fd9e906af23e3b,a4b7ec12298c78392797e5ba7704076550e4f100. ---------------------------------------- Bug #19444: YJIT String#+@ miscompilations https://bugs.ruby-lang.org/issues/19444#change-102183 * Author: alanwu (Alan Wu) * Status: Closed * Priority: Normal * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONE ---------------------------------------- We noticed two issues with YJIT's `String#+@` (String unary plus) implementation. 1. It has issues with GC allocation tracing. We saw it SEGV with the `Stackprof` gem 2. It has a type confusion issue from assuming that the method always return an `::String` instance. It can return subclass instances The YJIT override does not exist on the 3.1 series. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/