[#4479] Requesting addition to IRB (configurable standard output) — Sascha Ebach <se@...>

Hello,

13 messages 2005/02/24
[#4482] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/25

Quoting se@digitale-wertschoepfung.de, on Fri, Feb 25, 2005 at 01:22:34AM +0900:

[#4483] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/25

On 24 Feb 2005, at 19:51, Sam Roberts wrote:

[#4488] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/26

Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 02:43:31AM +0900:

[#4489] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/26

On 25 Feb 2005, at 16:03, Sam Roberts wrote:

Re: [BUG] Segmentation fault

From: Andrew Walrond <andrew@...>
Date: 2005-02-02 09:18:14 UTC
List: ruby-core #4358
Hi Ville

On Wednesday 02 February 2005 08:13, ville.mattila@stonesoft.com wrote:
>
> What optmization level you are using when compiling ruby? If it is O3, then
> this patch might help?
>
> Fri Jan  7 18:03:35 2005  Tanaka Akira  <akr@m17n.org>
>
>         * gc.c (mark_locations_array): avoid core dump with -O3.
>           [ruby-dev:25424]
>

I'm using -O2, so should be OK

>
> Also I think that we should study the information from
> http://rubyforge.org/tracker/index.php?func=detail&aid=1243&group_id=426&at
>id=1698
>
> there might be subtle 64 bit problems that are hidden because we do not see
> all compiler warnings...

Thanks for the pointer. 

"ruby defaults to using gcc c89 syntax. Use of -pedantic reveals ruby is using 
'long long' and 'inline'. Compiling with gcc -std=gnu99 solves a stack 
management problem in the code since gnu99 treats 'long long' as 64-bit. "

This certainly looks interesting. I wonder if it applies to x86_64, since I 
think the standard types have different sizes than ia64 (eg int=32bits, 
long=64bits on x86_64, but I think int=64bits on ia64?)

What do people think; Is "gcc -std=gnu99" worth a shot on x86_64 ?

Andrew

In This Thread