From: Yukihiro Matsumoto Date: 2007-11-23T11:30:09+09:00 Subject: Re: 1.8.6: gc.c and __builtin_frame_pointer Hi, In message "Re: 1.8.6: gc.c and __builtin_frame_pointer" on Fri, 23 Nov 2007 10:38:54 +0900, Jay Levitt writes: | |I'm playing with porting Ruby to Stratus VOS, which is an unusual but |POSIX-supporting x86 platform. | |My first build problem was a crash in miniruby, in gc.c. In a nutshell, |gc.c is relying on __builtin_frame_pointer but is not setting |-fno-omit-frame-pointer. This causes a crash, but I'm not sure what the |proper semantics of these two are and if I should (a) submit a patch for |Ruby in autoconf, or (b) submit a patch to Stratus for a bug in their gcc |implementation (currently at 3.3.1). For the workaround, you can try specifying --disable-frame-address to configure to see if it works. We'd welcome a patch to specify -fno-omit-frame-pointer when GCC is used on x86. matz.