From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Shrinking the C core Date: Sun, 20 Aug 2023 13:12:10 +0000 Message-ID: <87bkf197th.fsf@localhost> References: <87zg2uqdmv.fsf@localhost> <87edk3gbh3.fsf@dataswamp.org> <87jztvnuyb.fsf@localhost> <875y5bdutt.fsf@dataswamp.org> <87y1i6e1uh.fsf@localhost> <874jkub40o.fsf@dataswamp.org> <87jztqdw2l.fsf@localhost> <871qfyb172.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="35224"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: tomas@tuxteam.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 20 15:12:49 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 1qXiEb-0008xw-0D for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Aug 2023 15:12:49 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qXiDg-0003XU-Vi; Sun, 20 Aug 2023 09:11:52 -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 1qXiDe-0003XG-Vg for emacs-devel@gnu.org; Sun, 20 Aug 2023 09:11:50 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qXiDb-0001YS-Q0 for emacs-devel@gnu.org; Sun, 20 Aug 2023 09:11:50 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 954A2240103 for ; Sun, 20 Aug 2023 15:11:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1692537104; bh=fvc1rah6T1DJFxnZI3aVFM6NJP0bQWRd4o485Pgxg/8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=qyz5KgQ/8yr8OloBmR7nJQum4s1OftoYPAFuIx+eX+C2WGef8edo4z60GhR7m9JEK P77QYftlLHdVwQG8ijB9RTHjCt/ZROdy4hdi/UB1AhVbAS4GF0/ADHrtMXM8ZoWfhV XBGjN0zB3CoSaYSVyqjbmutq/I1pFPay4IHGrSkEyOcc2COERv/sPwSribARtWUgOZ CXsh3Ak3n0BWJ4XSUamizCyP3azXVuWjNXuRUZqu/J/9L1CqC2gTT6PrVnfFWhkgTn g9x45LAYQCBjFdysI8mSNjQeVIw3aS2TxQm8tzneKBi4GjXpOvwzANdEY1ZNTAV0C5 lXzslXxG0LTvw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RTGGS0hmSz9rxB; Sun, 20 Aug 2023 15:11:44 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -53 X-Spam_score: -5.4 X-Spam_bar: ----- X-Spam_report: (-5.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:308962 Archived-At: writes: > I humbly suggest you read up a bit on compilation. Those > type checks happen at compile time for a reason: the very > expensive data flow analysis provides the compiler with > information which is quite difficult to obtain later. > ... > but for that you have to take your program painstakingly > apart into basic blocks, take note of what leads to where > and think hard about which variables are munged where. Correct me if I am wrong, but don't we already make use of the extensive static analysis when native-compiling Elisp? AFAIU, the main problem with typechecks is that native-comp cannot do anything about subroutines, where a number of repetitive typechecks are performed. So, subroutine code cannot make use of the information provided by native-comp static analysis performed by GCC. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at