[#1] Welcome to the ruby-core mailing list — matz@... (Yukihiro Matsumoto)
Hi,
2 messages
2002/05/10
[#7] Useless patch... — Michal Rokos <m.rokos@...>
Hi,
6 messages
2002/05/14
[#19] Re: [BUG] thread failure after trap — nobu.nokada@...
Hi,
11 messages
2002/05/16
[#20] Re: [BUG] thread failure after trap
— ts <decoux@...>
2002/05/16
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#23] Re: [BUG] thread failure after trap
— nobu.nokada@...
2002/05/16
Hi,
[#42] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>
32 messages
2002/05/25
[#43] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/26
Hi,
[#45] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#46] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/26
Hi,
[#47] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#48] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/26
>>>>> "t" == ts <decoux@moulon.inra.fr> writes:
[#49] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#50] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#51] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#52] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#53] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#54] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#55] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/27
Hi,
[#56] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/27
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#57] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/28
Hi,
[#65] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/28
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#84] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#92] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#93] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#94] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#95] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/29
Hi,
[#96] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/29
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#59] yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...>
Would it be possible to add '-p ruby' to the bison command line args
8 messages
2002/05/28
[#60] Re: yyparse() and friends >> rubyparse() or rbparse()...
— matz@... (Yukihiro Matsumoto)
2002/05/28
Hi,
[#61] Re: yyparse() and friends >> rubyparse() or rbparse()...
— Sean Chittenden <sean@...>
2002/05/28
> |Would it be possible to add '-p ruby' to the bison command line
[#67] The warns-a-thon continues... — Sean Chittenden <sean@...>
I'm feeling left out in this race to clobber warnings!!! Attached are
19 messages
2002/05/28
[#69] Re: The warns-a-thon continues...
— matz@... (Yukihiro Matsumoto)
2002/05/28
Hi,
[#70] Re: The warns-a-thon continues...
— WATANABE Hirofumi <eban@...>
2002/05/28
Hi,
[#71] Re: The warns-a-thon continues...
— Sean Chittenden <sean@...>
2002/05/28
> :*) Fixed some sprintf() format type mismatches
[#86] rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...>
I'm doing a lot of work with Ruby in C and am using some of Ruby's
9 messages
2002/05/29
[#117] Re: rb_hash_has_key() and friends non-static...
— Sean Chittenden <sean@...>
2002/06/03
At the moment I'm writing an appendix Beginning Ruby Programming
[#119] Re: rb_hash_has_key() and friends non-static...
— nobu.nokada@...
2002/06/04
Hi,
[#104] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
29 messages
2002/05/30
[#105] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/30
Hi,
[#106] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/05/31
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#107] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/05/31
Hi,
[#125] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/04
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#126] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/04
Hi,
[#127] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/04
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#130] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/04
Hi,
[#132] Re: possible bug: stack dump with <<-String, #{...} and large loops
— nobu.nokada@...
2002/06/05
Hi,
[#134] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/05
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#135] Re: possible bug: stack dump with <<-String, #{...} and large loops
— ts <decoux@...>
2002/06/05
>>>>> "t" == ts <decoux@moulon.inra.fr> writes:
[#138] Re: possible bug: stack dump with <<-String, #{...} and large loops
— matz@... (Yukihiro Matsumoto)
2002/06/05
Hi,
[Cleanup] GC
From:
Michal Rokos <m.rokos@...>
Date:
2002-05-11 13:17:45 UTC
List:
ruby-core #3
Hi,
for the beginning I'll start with the very easy cleanup, just to
celebrate new mailing list.
(Thanks matz for this ML!)
Michal
Index: gc.c
===================================================================
RCS file: /src/ruby/gc.c,v
retrieving revision 1.92
diff -u -r1.92 gc.c
--- gc.c 2002/04/25 13:55:58 1.92
+++ gc.c 2002/05/11 12:46:32
@@ -1128,18 +1128,7 @@
struct gc_list *list;
struct FRAME * volatile frame; /* gcc 2.7.2.3 -O2 bug?? */
jmp_buf save_regs_gc_mark;
-#ifdef C_ALLOCA
- VALUE stack_end;
- alloca(0);
-# define STACK_END (&stack_end)
-#else
-# if defined(__GNUC__) && defined(USE_BUILTIN_FRAME_ADDRESS)
- VALUE *stack_end = __builtin_frame_address(0);
-# else
- VALUE *stack_end = alloca(1);
-# endif
-# define STACK_END (stack_end)
-#endif
+ SET_STACK_END;
if (dont_gc || during_gc) {
if (!freelist || malloc_memories > GC_MALLOC_LIMIT) {
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michal Rokos Czech Technical University, Prague
E-mail:m.rokos@sh.cvut.cz ICQ:36118339 Jabber:majkl@jabber.sh.cvut.cz
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-