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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 3D4E57ED99 for ; Mon, 25 May 2015 08:25:29 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of jezreel@gmail.com) identity=pra; client-ip=209.85.218.46; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jezreel@gmail.com"; x-sender="jezreel@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of jezreel@gmail.com designates 209.85.218.46 as permitted sender) identity=mailfrom; client-ip=209.85.218.46; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jezreel@gmail.com"; x-sender="jezreel@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-oi0-f46.google.com) identity=helo; client-ip=209.85.218.46; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jezreel@gmail.com"; x-sender="postmaster@mail-oi0-f46.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DvAwCgv2JVlC7aVdFchEIGgxnJHQc7EQEBAQEBAQERAQEBAQcLCwkfMEEEg1QiER0BGx4DEggBAgU3AiQBEQEFAVeHdAEDEp9DgzA+MYs+gWuCeZkKChknDVeEVQEFDpBOglKBRQWMQYdoiW6VZRIjgQwJhDseMYJHAQEB X-IPAS-Result: A0DvAwCgv2JVlC7aVdFchEIGgxnJHQc7EQEBAQEBAQERAQEBAQcLCwkfMEEEg1QiER0BGx4DEggBAgU3AiQBEQEFAVeHdAEDEp9DgzA+MYs+gWuCeZkKChknDVeEVQEFDpBOglKBRQWMQYdoiW6VZRIjgQwJhDseMYJHAQEB X-IronPort-AV: E=Sophos;i="5.13,489,1427752800"; d="scan'208";a="153699705" Received: from mail-oi0-f46.google.com ([209.85.218.46]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 25 May 2015 08:25:28 +0200 Received: by oiww2 with SMTP id w2so51590594oiw.0 for ; Sun, 24 May 2015 23:25:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=BpYt58DDfltVwmjDD5VJHMtatJWNk/a5uQHvwaHXeQo=; b=N3HHClShpbDCDgsFdMKANUa5AEWlgdrMv9F03NkoSmO6c0fngZNQz8E7+3i1rZMhdv xvzDW2tRaJd/jF7RuZj3pQTrir7XHm86c2ujOEYUZmz9mpPsTxro1EEH6uX2T50B+rZ0 WL1l0yPv44tOhKgLSaYkTTZ96QHeokPfvm3ZfuhfbSOKnvXTYdYqePEY5F05hat4XB/O dsjaO/tf0pvYG+jDZkU4pwZttDARJSjchisQ0kXex1Fm/zMKJX0YIPbeEspdKh5fuohi 9o3lm7OAJjqwFV3n1a+i+Z8kKkJAai7i01QXHekBLgjOvxE5dRHCSAox416YMatpjjy3 ecuw== X-Received: by 10.182.47.225 with SMTP id g1mr3914576obn.82.1432535127285; Sun, 24 May 2015 23:25:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.100.173 with HTTP; Sun, 24 May 2015 23:25:07 -0700 (PDT) From: Jez Date: Sun, 24 May 2015 23:25:07 -0700 Message-ID: To: caml-list@inria.fr Content-Type: multipart/alternative; boundary=089e0158ada263ef100516e21339 Subject: [Caml-list] When to (not) use -no-naked-pointers? --089e0158ada263ef100516e21339 Content-Type: text/plain; charset=UTF-8 Hi, I noticed that 4.02 now has the no-naked-pointers option. I'd like to better understand when I shouldn't use it -- i.e. what kinds of operations create naked pointers? I suppose that these pointers can only be generated by C code; an example of when their use may arise would be nice :) Jez --089e0158ada263ef100516e21339 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I noticed that 4.02 now has the no-= naked-pointers option. I'd like to better understand when I shouldn'= ;t use it -- i.e. what kinds of operations create naked pointers? I suppose= that these pointers can only be generated by C code; an example of when th= eir use may arise would be nice :)

Jez
--089e0158ada263ef100516e21339--