caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: Shuai Wang <wangshuai901@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Cannot execute "main" function
Date: Fri, 17 Jul 2015 14:57:07 -0400	[thread overview]
Message-ID: <CAK7rcp-7XvVqkHo1a0N3JfAe1uk5kmubnUCFZn7tGQgRmtVniQ@mail.gmail.com> (raw)
In-Reply-To: <CAEQMQomKQS==wzWN_ps=_z36fmESu8t=cynr+i9f9-_Av5G2KA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]

Right, I was wondering if I should tell you that. That means:

let _ =
  my main definition...

or

let () =
  my main definition...

each get evaluated very similarly to how a main function would. Is there
code that you can post in order that I/we can help you?

On Fri, Jul 17, 2015 at 2:53 PM, Shuai Wang <wangshuai901@gmail.com> wrote:

> Here is my compilation script.
>
> ocamlbuild -use-ocamlfind  XXX1.native XXX2.native ... init.native
>  -ocamlopt "-inline 20" -ocamlopt -nodynlink
>
> And our tool always execute init.native.
>
>
>
>
> On Fri, Jul 17, 2015 at 2:50 PM, Kenneth Adam Miller <
> kennethadammiller@gmail.com> wrote:
>
>> Can you post your build specification?
>>
>> On Fri, Jul 17, 2015 at 2:35 PM, Shuai Wang <wangshuai901@gmail.com>
>> wrote:
>>
>>> Dear list,
>>>
>>>
>>> I am working on some tools written in OCaml (compiled by OCaml version
>>> 4.01.0).
>>>
>>> This morning I changed some code, compiled it and let it processing some
>>> large data (~ 4G), it never stops after over 2 hours.
>>>
>>> I feed the tool with a tiny input which took less than 1 second to
>>> process before, and  I figured out that now it takes around 2.5 minutes
>>> before entering into "main" function!
>>>
>>> I tried to clean the whole codebase, and recompile it ( I use ocamlbuild
>>> 4.01.0), but the same wired situation still happens..
>>>
>>> I did this:
>>>
>>>     ltrace ./init.native input
>>>
>>> and I got this output flushing out for a very long time (sorry mail list
>>> blocks my large image.. ):
>>>
>>> http://i.stack.imgur.com/sEkKk.png
>>>
>>>
>>>
>>> Is anyone aware this kind of issue before..? Am I messed up something..?
>>> I have been working on OCaml for a relatively long time and I didn't
>>> encounter this kind of stuff before...
>>>
>>>
>>> Sincerely,
>>> Shuai
>>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 4361 bytes --]

  reply	other threads:[~2015-07-17 18:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 18:35 Shuai Wang
2015-07-17 18:50 ` Kenneth Adam Miller
2015-07-17 18:53   ` Shuai Wang
2015-07-17 18:57     ` Kenneth Adam Miller [this message]
2015-07-17 19:08       ` Shuai Wang
2015-07-17 18:51 ` Ivan Gotovchits
2015-07-17 19:07   ` Shuai Wang
2015-07-17 19:11     ` Ivan Gotovchits
2015-07-17 19:13       ` Shuai Wang
2015-07-17 19:16         ` Kenneth Adam Miller
2015-07-17 19:35           ` Shuai Wang
2015-07-17 19:37             ` Kenneth Adam Miller

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=CAK7rcp-7XvVqkHo1a0N3JfAe1uk5kmubnUCFZn7tGQgRmtVniQ@mail.gmail.com \
    --to=kennethadammiller@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=wangshuai901@gmail.com \
    /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).