[#5219] Segmentation fault in timeout.rb — Michel Pastor <K@...>

Hi,

18 messages 2005/06/16
[#5220] Re: Segmentation fault in timeout.rb — Eric Hodel <drbrain@...7.net> 2005/06/16

[#5221] Re: Segmentation fault in timeout.rb — Michel Pastor <K@...> 2005/06/16

On Fri, 17 Jun 2005 05:03:18 +0900

[#5223] Re: Segmentation fault in timeout.rb — nobu.nokada@... 2005/06/17

Hi,

[#5296] Subversion — Shugo Maeda <shugo@...>

Hi,

64 messages 2005/06/30
[#5297] Re: Subversion — Curt Hibbs <curt@...> 2005/06/30

Shugo Maeda wrote:

[#5298] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/06/30

Curt Hibbs wrote:

[#5301] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, Nikolai Weibull

[#5304] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/06/30

Austin Ziegler wrote:

[#5305] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, Nikolai Weibull

[#5307] Re: Subversion — mathew <meta@...> 2005/06/30

Austin Ziegler wrote:

[#5308] Re: Subversion — Austin Ziegler <halostatue@...> 2005/06/30

On 6/30/05, mathew <meta@pobox.com> wrote:

[#5311] Re: Subversion — mathew <meta@...> 2005/07/01

Austin Ziegler wrote:

[#5323] Re: Subversion — Austin Ziegler <halostatue@...> 2005/07/01

On 7/1/05, mathew <meta@pobox.com> wrote:

[#5325] Re: Subversion — Nikolai Weibull <mailing-lists.ruby-core@...> 2005/07/01

Austin Ziegler wrote:

Re: [PATCH] 1.8.3 p1 segfault in array.c- bccwin32 - bcc5.5 (free) compiler bug

From: "daz" <dooby@...10.karoo.co.uk>
Date: 2005-06-28 04:05:21 UTC
List: ruby-core #5286
I discussed this on the Borland forum[*] and it was confirmed as an
optimizer bug.

I guess that Ocean and the bccwin team are wondering why they haven't
seen this problem.  The reason is ...

Command line option /v (lower case) embeds debugging information in
the object file __and__ arranges inline functions to be function calls.
The default for this option in bcc55 is ON -- therefore, the CLASS_OF
and TYPE (and other?) macros each result in function calls.

I don't need debugging info because there aren't any bugs in Ruby ;-)
As a bonus for setting /v- , all inline code is, actually, inline.

Like most people, I prefer slower code to segfaults, so I'll have to
revert to the default option, for now.  However, I think that this
option should be OFF for bccwin Ruby builds and that a workaround
should be chosen for the SEGV (many are available).

I'll let Ocean, or someone else, decide on that when they've noticed
the speed increase after removing their overheads.


daz
-- 
JARH (Nihon-style) ... not as simple as you might think.
http://qurl.net/h3 (babelfish)
http://qurl.net/h7 (excite jp)


[*] (not recommended reading)
http://groups.google.com/groups?threadm=42aa5aa9$1@newsgroups.borland.com





In This Thread