regarding ia64 weirdness.

[Aredridel]

----- Forwarded message from Jakub Bogusz <[email protected]> -----

From: Jakub Bogusz <[email protected]>
Reply-To: "PLD: Developers list \(English\)" <[email protected]>
To: "PLD: Developers list (English)" <[email protected]>
Date: Mon, 26 Jul 2004 20:11:21 +0200
Subject: Re: SPECS: ruby.spec - document ia64 bug better,
so it can be examined...

Asked about on (e-mail address removed). I'll add a patch if someone has
information.

It's something strange, probably some bug causing memory corruption.
In gc.c there is some "magic stack limit" applied on ia64 (which is too
low to build ruby now anyway), but it doesn't change anything when code
is compiled with -O1 or -O2.
With -O2 miniruby fails with "unexpected break".
With -O1 catches SIGSEGV.
Adding -fno-strict-aliasing doesn't help.

Builds only with -O0 and "magic stack limit" disabled.

I've googled a bit and found that:
- RH/Fedora and SuSE use -O0 and have ruby on ia64,
- Gentoo and some BSD marked ia64 port as broken.


--
Jakub Bogusz http://cyber.cs.net.pl/~qboosh/

_______________________________________________
pld-devel-en mailing list
(e-mail address removed)
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

----- End forwarded message -----