From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Introducing 'safety' compilation parameter Date: Fri, 10 May 2024 14:02:42 -0400 Message-ID: References: <86a5kz74yw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7427"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, mattias.engdegard@gmail.com, stefankangas@gmail.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 10 20:03:03 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s5UaE-0001fT-V1 for ged-emacs-devel@m.gmane-mx.org; Fri, 10 May 2024 20:03:03 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s5Ua1-0007fI-Df; Fri, 10 May 2024 14:02:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s5Ua0-0007eS-8r for emacs-devel@gnu.org; Fri, 10 May 2024 14:02:48 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s5UZy-0005BN-UY; Fri, 10 May 2024 14:02:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=KhkhYRnGh2IvlYgXX1eG2oYer0AyY1dHkm6hFKQqLa0=; b=o+YozQfPavhb4twdd6bH 9dtS7Jt+whqen2GhaIsezWQUnBFF5zkuIaonjCBAEeZaYtQqaeyTAxl+U5hDXgKsatYTX9XRAPdEk IqvCeQ5p9CBolM0K0zBFm5p87XxCRTs0K2gdOh0SIt2Oviy53E2n0C/EWLl4BPUL1rz6r2Ql5xVg0 APKFMY1N0pc/grilq0lFXehNur7EFUbrg9JzApJmu96aWOT6bsrcrY2mhATvbUn3nrU8b4Nelvru3 /opeOlEgT895ZGvV4BF4L0KIbVot7REaAmeaZN0OLUFUhSIAlkwakstvlme9zZFxwMiF3syxyGMRz 6tYaIqRXkgd8SA==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1s5UZw-00049z-3p; Fri, 10 May 2024 14:02:46 -0400 In-Reply-To: <86a5kz74yw.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 May 2024 11:40:55 +0300") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319154 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: Eli Zaretskii , monnier@iro.umontreal.ca, >> mattias.engdegard@gmail.com, stefankangas@gmail.com >> Date: Tue, 07 May 2024 06:37:50 -0400 >> >> I've put in scratch/comp-safety a branch wich introduces 'safety' as >> compilation parameter. >> >> 'safety' can be used similarly to 'native-comp-speed' both as a global >> variable to influence compilation both as a function declaration. >> >> 'safety' justification of existence is ATM being able to control the >> undefined behaviour being created when function type declaration added >> by the user is not correct. >> >> ATM we can have two values: >> >> 1 Emitted code is generated in a safe matter even if function types are >> miss-declared. >> 0 Emitted code can misbehave or crash Emacs if function declarations are >> not correct and the function is native compiled (@pxref{Native >> Compilation}). >> >> 1 is ATM the default. > > Is this for Emacs 30 or Emacs 31? > > If the former, we should conclude this discussion soon enough. > > I don't have an opinion about the utility of this for Emacs Lisp, but > this part of the documentation: > >> +Possible values are: >> + >> +0 Emitted code can misbehave or crash Emacs if function declarations are >> +not correct and the function is native compiled (@pxref{Native >> +Compilation}). >> + >> +1 Emitted code is generated in a safe matter even if function are >> +miss-declared." > > should be formatted as a @table. Okay, I moved that part to doc/lispref/compile.texi to document in 'compilation-safety' and added the @table for the possible values. Still in functions.texi we keep a reference to it. Thanks Andrea