From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id A17A77F75C for ; Thu, 25 Sep 2014 05:50:57 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of trigger0219@gmail.com) identity=pra; client-ip=209.85.192.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="trigger0219@gmail.com"; x-sender="trigger0219@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of trigger0219@gmail.com designates 209.85.192.51 as permitted sender) identity=mailfrom; client-ip=209.85.192.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="trigger0219@gmail.com"; x-sender="trigger0219@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qg0-f51.google.com) identity=helo; client-ip=209.85.192.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="trigger0219@gmail.com"; x-sender="postmaster@mail-qg0-f51.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgcCAKaQI1TRVcAzlGdsb2JhbABgg2FXBIJ9tgaPWIFvh0yBBAgWAREBAQEBBwsLCRIthAQBAQMBEhEEGQEbEgsBAwELAQUFCxoaAwICIgERAQUBCgERBxISEIgHAQMJCA2hWW6LMIFygxCJLgoZJwMKZoY7EQEFDpAMgwOBUwEEhRMFjUuDNYcJgWGSARgpgWyDQyEvAYJJAQEB X-IPAS-Result: AgcCAKaQI1TRVcAzlGdsb2JhbABgg2FXBIJ9tgaPWIFvh0yBBAgWAREBAQEBBwsLCRIthAQBAQMBEhEEGQEbEgsBAwELAQUFCxoaAwICIgERAQUBCgERBxISEIgHAQMJCA2hWW6LMIFygxCJLgoZJwMKZoY7EQEFDpAMgwOBUwEEhRMFjUuDNYcJgWGSARgpgWyDQyEvAYJJAQEB X-IronPort-AV: E=Sophos;i="5.04,594,1406584800"; d="scan'208";a="80806891" Received: from mail-qg0-f51.google.com ([209.85.192.51]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 25 Sep 2014 05:50:56 +0200 Received: by mail-qg0-f51.google.com with SMTP id a108so6900550qge.24 for ; Wed, 24 Sep 2014 20:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=DleJeGqa5pXP/+PJCTV/vqryh6EDEeFe12MJXe+GX8Y=; b=XCE2oNd1Tk3fLwbgMnbi7vjc3T9UlvijCIDlfFkqZnemXboVUWRI1Qk5rsT18WF4Xp 2MQ7KkFY6n3Utz0eP7wkYz0dscNFVCnd0EjeMBqS/KkWQssxAW5KhRfKbl+wEjyjgb+p pmfFcSifSS+ySRNFvS5VzjJ3yDBBJ+L2BB4TjqOTuTYA007hZAEalWiF9qHIsYEsWH8g vEXaiO63LrABwhfkMfVcRtQ6utjMP7K23DLkNKeE4HBBMyNLoFZJCxBJSKjETyfph10/ eSs8RSe6PK4zcS1PQq2njbbmBax77pTdOoKJqWrHFHT6PG//MiyeBpy/psA0dNxbJ/t3 /dRw== X-Received: by 10.224.51.197 with SMTP id e5mr14953612qag.48.1411617055009; Wed, 24 Sep 2014 20:50:55 -0700 (PDT) MIME-Version: 1.0 Sender: trigger0219@gmail.com Received: by 10.229.91.69 with HTTP; Wed, 24 Sep 2014 20:50:14 -0700 (PDT) In-Reply-To: <87r3z2720e.fsf@comtv.ru> References: <87r3z2720e.fsf@comtv.ru> From: Nick Lucaroni Date: Wed, 24 Sep 2014 23:50:14 -0400 X-Google-Sender-Auth: ZUX5dcXqEVI9gZkOQFGJ61iAhzI Message-ID: To: av1474@comtv.ru, caml-list@inria.fr Cc: Damien Doligez Content-Type: multipart/alternative; boundary=001a11c2d35e1f73640503dbb5c3 Subject: Re: [Caml-list] OCaml 4.02.1 is coming soon --001a11c2d35e1f73640503dbb5c3 Content-Type: text/plain; charset=UTF-8 Are the formatting issues resolved in the 4.02.0+turnk switch in OPAM (that's, dev0-2014-08-29)? I'm getting segmentation faults from fprintf in my application even in that branch (see below). I'll work to pin it down as it very well could be a miss-formatted string on my part, but obviously we shouldn't seg-fault. let me know if I should hold off. thanks, nick Time: 48706621 - pc: 98976 - module CamlinternalFormat 1375 fun k o acc fmt -> <|b|>match fmt with On Tue, Sep 23, 2014 at 12:08 PM, wrote: > Damien Doligez writes: > > > Dear OCaml users, > > > > The rather large amount of changes in the newly released 4.02 > > inevitably caused some issues in the very first minor release. We > > shall have a 4.02.1 bugfix release coming soon, hopefully in early > > October. > > > > Among the few issues that have now been fixed, there are a few > > regressions in the new, type-safe format implementation > > (Printf/Scanf/Format) -- for advanced formatting features. > > > > There was also a regression in the *compilation time* of the > > distributed OCaml compiler, which is sensibly slower than 4.01 on > > multi-module programs. This is already fixed in the development > > version of the compiler and will be part of the bugfix release. > > > > Compilation of [1] skyrocketed (at least here on rather oldish PPC > machine), hopfully things would be a bit better in 4.02.1. > > > Any additional testing to find and report other regressions is more > > than welcome. If you have not yet tested your programs with 4.02, now > > is the time to give it a try! > > > > > > -- Damien > > [1] > http://repo.or.cz/w/llpp.git/blob/53f1bca0140d03d9f2e1437a4ad0dbc3f7e85ce0:/main.ml > -- > mailto:av1474@comtv.ru > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > --001a11c2d35e1f73640503dbb5c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Are the formatting issues resol= ved in the 4.02.0+turnk switch in OPAM (that's, dev0-2014-08-29)? I'= ;m getting segmentation faults from fprintf in my application even in that = branch (see below). I'll work to pin it down as it very well could be a= miss-formatted string on my part, but obviously we shouldn't seg-fault= . let me know if I should hold off.

thanks,
nick<= /div>

Time: 48706621 - pc: 98976 - module CamlinternalFormat=
1375 fun k o acc fmt -> <|b|>= match fmt with



On Tue, Sep 23, 2014 at 12:08 PM, <av1474@comtv.ru> wrote:
Damien Doligez <damien.doligez@inria.fr> writes:
> Dear OCaml users,
>
> The rather large amount of changes in the newly released 4.02
> inevitably caused some issues in the very first minor release. We
> shall have a 4.02.1 bugfix release coming soon, hopefully in early
> October.
>
> Among the few issues that have now been fixed, there are a few
> regressions in the new, type-safe format implementation
> (Printf/Scanf/Format) -- for advanced formatting features.
>
> There was also a regression in the *compilation time* of the
> distributed OCaml compiler, which is sensibly slower than 4.01 on
> multi-module programs. This is already fixed in the development
> version of the compiler and will be part of the bugfix release.
>

Compilation of [1] skyrocketed (at least here on rather oldish PPC
machine), hopfully things would be a bit better in 4.02.1.

> Any additional testing to find and report other regressions is more
> than welcome. If you have not yet tested your programs with 4.02, now<= br> > is the time to give it a try!
>
>
> -- Damien

[1] http://repo.or.cz/w/llpp.git/blo= b/53f1bca0140d03d9f2e1437a4ad0dbc3f7e85ce0:/main.ml
--
mailto:av1474@comtv.ru=

--
Caml-list mailing list.=C2=A0 Subscription management and archives:
ht= tps://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

--001a11c2d35e1f73640503dbb5c3--