From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Add more supported primitives in libgccjit IR Date: Mon, 28 Aug 2023 00:19:25 +0200 Message-ID: <87y1hwqgb6.fsf@dataswamp.org> References: <20230809094655.793FC18A4654@snark.thyrsus.com> <87edjx7c0b.fsf@localhost> <831qfxw2cx.fsf@gnu.org> <87v8d95918.fsf@localhost> <87zg2lav4b.fsf@yahoo.com> <87sf8d57wf.fsf@localhost> <87r0nxatu1.fsf@yahoo.com> <87pm3h56ig.fsf@localhost> <87edjxarhz.fsf@yahoo.com> <87edjw4uw4.fsf@localhost> <77daee02cf1ba0db70c1@heytings.org> <87v8d8fzr9.fsf@localhost> <87jztofwqm.fsf@localhost> <83cyzgvb70.fsf@gnu.org> <87cyze6pb4.fsf@localhost> <87y1hx460x.fsf@dataswamp.org> <874jklrl37.fsf@dataswamp.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="29184"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:NbTVrip8Dbw8Bh1WFGCK0gDP9SI= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 28 04:20:08 2023 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 1qaRrM-0007MT-1B for ged-emacs-devel@m.gmane-mx.org; Mon, 28 Aug 2023 04:20:08 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaRqN-0007v0-JC; Sun, 27 Aug 2023 22:19:07 -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 1qaO6f-0000mG-2o for emacs-devel@gnu.org; Sun, 27 Aug 2023 18:19:41 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qaO6c-0001FD-6m for emacs-devel@gnu.org; Sun, 27 Aug 2023 18:19:40 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qaO6Z-000AJM-8D for emacs-devel@gnu.org; Mon, 28 Aug 2023 00:19:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sun, 27 Aug 2023 22:19:06 -0400 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:309394 Archived-At: Andrea Corallo wrote: >>> The only trace I have been able to find of either are >>> functions in C, built-in functions in the Emacs lingo, for >>> example `+', if you do `describe-function' on that you see >>> in the docstring >>> >>> Type: (function (&rest (or marker number)) number) >> >> Lisp functions also get their types inferred, sometimes, > > AFAIK all native compiled Lisp functions are type inferred. You are right, those who don't have types are those that are only byte-compiled! But then why are they not native-compiled as well? I think the functions inside lexical let-closures, i.e. (let (( ... )) (defun ... ) ) are not natively compiled. See the file that I yank last, none of those functions are or get natively-compiled. Note the `declare-function' lines; those are there so the byte-compiler will not complain these functions are not defined - which they are - so maybe the problem starts already at the byte-compilation step. >> Maybe function that are made up of functions that have >> their types inferred also get their types inferred ... > > Of course they are typed as well, but we can use the types > of the called functions for propagations as they can be > redefined in every moment. We can? Please explain, let's say we have this f(x) = a(b(c(x))) a, b, and c are natively-compiled and type inferred, so the type of f is known this way. But if a, b, and c are redefined and their types are changed to the point f also has a type change, how can we know that? If type inference happens at native-compile time, how do we know when executing f that, because a, b, and c has changed, the old type of f no longer holds? -- underground experts united https://dataswamp.org/~incal