caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andres Varon <avaron@gmail.com>
To: Alain Frisch <alain@frisch.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] segfault in 3.10.0
Date: Thu, 2 Aug 2007 13:31:41 -0400	[thread overview]
Message-ID: <99FED25B-43AA-4FE1-B3E8-257358A9B77A@gmail.com> (raw)
In-Reply-To: <46B20A54.2050702@frisch.fr>


On Aug 2, 2007, at 12:46 PM, Alain Frisch wrote:

> Andres Varon wrote:
>> 1. The segfault is eliminated if I use position-dependent machine  
>> code
>> (-fno-PIC), which is the main difference that I can see in the
>> generated code for amd-64 between 3.09.3 and 3.10.0 (-fPIC is the
>> default now). When using -fno-PIC there was little difference between
>> the code spilled using -dlinear between the two versions. (I could  
>> not
>> get my program to compile with the branch release310 (3.10.1+dev0
>> (2007-05-21)) due to a type error that ... ehm ... isn't really a  
>> type
>> error ;-) ).
>
> It would be very helpful if you could try to compile your code with  
> the natdynlink branch (based on OCaml 3.10.0). The new -dlcode  
> option triggers a different compilation mode (real PIC code, even  
> for OCaml symbols).

OK, I cvs update -r natdynlink on top of the branch ocaml3100. I  
tried compiling native code with and without the -dlcode option, and  
in both cases I had the same segfault, in the same place.

Let me know if I can do other tests here.

Andres

>
> -- Alain
>


      reply	other threads:[~2007-08-02 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 21:10 Andres Varon
2007-08-01 22:27 ` [Caml-list] " Andres Varon
2007-08-02  0:39   ` Yaron Minsky
2007-08-02  5:05 ` Markus Mottl
2007-08-02 15:41   ` Andres Varon
2007-08-02 16:46     ` Alain Frisch
2007-08-02 17:31       ` Andres Varon [this message]

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=99FED25B-43AA-4FE1-B3E8-257358A9B77A@gmail.com \
    --to=avaron@gmail.com \
    --cc=alain@frisch.fr \
    --cc=caml-list@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).