Jeremy Evans <c...@jeremyevans.net> wrote: > On 07/24 01:25, Eric Wong wrote: > > Jeremy Evans <c...@jeremyevans.net> wrote: > > > Running with GC.stress didn't catch the error for me. But I'm using a > > > fairly old compiler (GCC 4.2.1, the OpenBSD default), so this may be > > > something that only shows up on a newer compiler that does more > > > optimizations. > > > > Pere: just curious if you've had a chance to test my patch for > > sequel_pg from Jeremy's latest sequel_pg.git > > > > In any case, I'm certain my patch fixes a bug which manifests > > in a compiler-dependent manner; but here could always be other > > bugs in a similar vein. Thanks. > > I can't get it to crash with sequel_pg 1.7.0 when compiled using clang > 4.0.0 either. I even tried to build a special program designed to > trigger the crash.
>From anecdotes on ruby-core, clang still seems less aggressive at optimizations than modern gcc. Fwiw, a few GC bugs in Ruby trunk got fixed recently and the fixes should be in 2.4.2 (soon): https://public-inbox.org/ruby-core/?q=T_NONE+d%3A20161225..20170808 Not identical to T_NODE which Pere got, but if it's a GC bug, but both T_NONE and T_NODE triggers are symptoms of GC bugs. -- unsubscribe: unicorn-public+unsubscr...@bogomips.org archive: https://bogomips.org/unicorn-public/
