caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Pixel <pixel@mandrakesoft.com>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Segv while compiling ocaml-3.04
Date: 22 Dec 2001 15:44:07 +0100	[thread overview]
Message-ID: <lyofkrmi14.fsf@leia.mandrakesoft.com> (raw)
In-Reply-To: <20011221140107.A26653@pauillac.inria.fr>

Xavier Leroy <xavier.leroy@inria.fr> writes:

[...]

> For those who are worried about it, the purity of the OCaml source
> code isn't affected: the patch simply selects gcc compilation options
> (-fomit-frame-pointer) that seem to work around the bug.

I find it quite funny that *adding* an optimisation makes things work. Since
2.96 (also true for 3.0), gcc has been much better at tail-call'ing,
tail-recursion. Most of the bugs appearing in 2.96 were caused by using "-O3"
together with "-fomit-frame-pointer". The solution was to *remove*
"-fomit-frame-pointer"

For information, i've had problems with ocaml 3.02 built with -O3
-fomit-frame-pointer. -O3 works nicely.

> As to which versions of gcc are affected: gcc 2.96 from RH 7.2 and
> Mandrake 8.1 are,

I've not been able to reproduce under 8.1 
(taking your srpm and removing the patch)

Mandrake and Redhat have been using gcc 2.96 for quite a long time now.
Mandrake 8.0 and redhat 7.1 have it. But beware that these gcc's are heavily
patched and evolved a lot.

[...]

> I'm certain that 2.95.2 is not, and believe that 3.0
> isn't either, but this has to be checked carefully.

3.0 is not very stable. Redhat's rawhide has switched to pre-3.1 cvs version.

About version gcc versions, check http://www.bero.org/gcc296.html
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-12-22 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200112170931.KAA0000003112@beaune.inria.fr>
2001-12-17  9:02 ` Christophe Raffalli
2001-12-21 13:01   ` Xavier Leroy
2001-12-22 14:44     ` Pixel [this message]
2001-12-23  8:37       ` Xavier Leroy
2001-12-14  8:39 Christophe Raffalli
2001-12-14 13:25 ` Pixel
     [not found] ` <15385.61778.52293.648002@gargle.gargle.HOWL>
     [not found]   ` <3C1A07E9.B01890D5@univ-savoie.fr>
     [not found]     ` <15386.19382.239731.32280@hector.lesours>
2001-12-15 10:32       ` Christophe Raffalli
2001-12-20 10:50 ` Xavier Leroy
2001-12-20 11:00   ` Christophe Raffalli
2001-12-20 22:49   ` Ian Zimmerman
2001-12-21  8:22     ` Florian Hars
2001-12-21  8:28       ` Ian Zimmerman
2001-12-21  9:25       ` William Chesters
2001-12-21 10:00         ` Sven
2001-12-21  8:24     ` Luc Maranget

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=lyofkrmi14.fsf@leia.mandrakesoft.com \
    --to=pixel@mandrakesoft.com \
    --cc=caml-list@inria.fr \
    --cc=gbeauchesne@mandrakesoft.com \
    --cc=xavier.leroy@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).