From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=AWL,HTML_MESSAGE autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id CDDB1BBAF for ; Wed, 17 Dec 2008 09:47:44 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlMCACRLSElRZ90xkWdsb2JhbACCb4o8hi8BAQEBCQsKBxEDqGtYkSeDBA X-IronPort-AV: E=Sophos;i="4.36,236,1228086000"; d="scan'208,217";a="18568190" Received: from mtaout03-winn.ispmail.ntl.com ([81.103.221.49]) by mail2-smtp-roc.national.inria.fr with ESMTP; 17 Dec 2008 09:47:44 +0100 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20081217084743.FPDM1691.mtaout03-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com>; Wed, 17 Dec 2008 08:47:43 +0000 Received: from romulus.metastack.com ([81.102.132.77]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20081217084743.PVKG19264.aamtaout01-winn.ispmail.ntl.com@romulus.metastack.com>; Wed, 17 Dec 2008 08:47:43 +0000 Received: from Countertenor (genkt-048-051.t-mobile.co.uk.254.149.in-addr.arpa [149.254.48.51] (may be forged)) (authenticated bits=0) by romulus.metastack.com (8.14.2/8.14.2) with ESMTP id mBH8lbe8010345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 17 Dec 2008 08:47:39 GMT From: "David Allsopp" To: "'Reed Wilson'" , References: In-Reply-To: Subject: RE: [Caml-list] Freeze in 64-bit Windows Num module Date: Wed, 17 Dec 2008 08:47:30 -0000 Organization: MetaStack Solutions Ltd. Message-ID: <00c801c96024$1aa9baf0$4ffd30d0$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C9_01C96024.1AA9BAF0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AclgFBaB0s1X6xyNR5uSh+TNSl6eJwAD8mbQ Content-Language: en-gb X-Scanned-By: MIMEDefang 2.64 on 81.102.132.74 X-Cloudmark-Analysis: v=1.0 c=1 a=VNTdyvZy7YwA:10 a=1WMGOgsiJXsA:10 a=vDdgutE4p81bhhVw_YsA:9 a=WjDR3byrb6k2n8_UwmIA:7 a=tBxeM6x4k8RYsDoFq1xamjsY4BcA:4 a=miwkIDoJte0A:10 a=2zl6NSEY7M9Mwgzk:21 a=xXsWjj-f1XObwdPu:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=usuKz3dG4Ykciaa-wGkA:9 a=XpXvGtG7Yp4Hr5GPwV8A:7 a=KivQ0CyejPHoUdijJkMlHeWQc2MA:4 a=37WNUvjkh6kA:10 X-Spam: no; 0.00; ocaml:01 bytecode:01 ocaml:01 bug:01 bytecode:01 bug:01 binaries:01 binaries:01 compile:01 compile:01 compiles:01 compiles:01 caml-list:01 caml-list:01 int:01 X-Attachments: cset="utf-8" cset="utf-8" This is a multipart message in MIME format. ------=_NextPart_000_00C9_01C96024.1AA9BAF0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I=E2=80=99m seeing the same thing... =20 =20 David =20 From: caml-list-bounces@yquem.inria.fr = [mailto:caml-list-bounces@yquem.inria.fr] On Behalf Of Reed Wilson Sent: 17 December 2008 06:53 To: caml-list@yquem.inria.fr Subject: [Caml-list] Freeze in 64-bit Windows Num module =20 Hi guys, =20 I have an issue with using the Num module in my Win64 OCaml compile. = Whenever I try to operate on numbers that are too large it will lock up. = For example, using: =20 string_of_num (num_of_int max_int */ num_of_int max_int) =20 causes the program to lock up with 100% CPU usage. This occurs in both = native and bytecode programs, and it has happened with both my 3.10.2 = and 3.11.0 compiles. The 32-bit Windows MSVS binaries on the OCaml = website work, as do my 64-bit Linux and OS-X builds of 3.11.0. =20 Before I submit this as a bug, can anyone who also has a 64-bit OCaml = compile in Windows verify this? =20 Thanks, Reed --=20 =C3=A7 ------=_NextPart_000_00C9_01C96024.1AA9BAF0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

I=E2=80=99m= seeing the same thing...

 =

 =

David<= /o:p>

 =

From: caml-list-bounces@yquem.inria.fr [mailto:caml-list-bounces@yquem.inria.fr] On Behalf Of Reed = Wilson
Sent: 17 December 2008 06:53
To: caml-list@yquem.inria.fr
Subject: [Caml-list] Freeze in 64-bit Windows Num = module

 

Hi guys,

 

I have an issue with using the Num module in my = Win64 OCaml compile. Whenever I try to operate on numbers that are too large it will = lock up. For example, using:

 

string_of_num (num_of_int max_int */ num_of_int = max_int)

 

causes the program to lock up with 100% CPU usage. = This occurs in both native and bytecode programs, and it has happened with = both my 3.10.2 and 3.11.0 compiles. The 32-bit Windows MSVS binaries on = the OCaml website work, as do my 64-bit Linux and OS-X builds of = 3.11.0.

 

Before I submit this as a bug, can anyone who also = has a 64-bit OCaml compile in Windows verify this?

 

Thanks,

Reed


--
=C3=A7

------=_NextPart_000_00C9_01C96024.1AA9BAF0--