From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Excessive use of `eassert`
Date: Sun, 21 Jan 2024 11:57:56 +0200
Message-ID: <838r4jrot7.fsf@gnu.org>
References: <jwvsf2u5l8j.fsf-monnier+emacs@gnu.org> <83jzo5x0q8.fsf@gnu.org>
 <jwveded5vrf.fsf-monnier+emacs@gnu.org> <83sf2tv029.fsf@gnu.org>
 <ZarQr591SsuIZwNs@ACM> <811d5f03-fad4-47e1-b3fd-2f45229a5ee1@cs.ucla.edu>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="1131"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: acm@muc.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org
To: Paul Eggert <eggert@cs.ucla.edu>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 21 10:58:56 2024
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
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 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1rRUbQ-000Ads-J3
	for ged-emacs-devel@m.gmane-mx.org; Sun, 21 Jan 2024 10:58:56 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1rRUaq-00008t-66; Sun, 21 Jan 2024 04:58:21 -0500
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 <eliz@gnu.org>) id 1rRUak-00008b-4l
 for emacs-devel@gnu.org; Sun, 21 Jan 2024 04:58:14 -0500
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 <eliz@gnu.org>)
 id 1rRUai-0001ol-Ru; Sun, 21 Jan 2024 04:58:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=FqBpoRp6K0KIzPH9adqdIMNwUCsGnflxsSvU/gSeh8o=; b=rYzVaC1PmoQr
 SaKiG3hAOW2/jxdlFqK6cy2HuE1o5RPEzMX2eVIRVMj6WhAMpk1oKQeasHTohlMjJ5TsDRJiq2iIG
 ZYZkD7eT7CjCfUYryl5lmU9AKVTgHgjShyoZikRuBqw1upVfv1Bn98FCfgopM8YdJSABl2pGNbA+q
 YzkO4md9hWnFzg2RVxQgvzkcM+qX1B+48B/SvVc3B6iSUo2p6N1jl3pj1pEOztQ+NnQmKnIonqU5L
 yobSn46UaWj+ad+j07D9abGkZ314i2MtJaZXgdtexivt+lCWe1K4mTJbaJ5UT0wbf1t10ZG16j+VL
 vtZZoZA37Vgy3aoW9gs7kw==;
In-Reply-To: <811d5f03-fad4-47e1-b3fd-2f45229a5ee1@cs.ucla.edu> (message from
 Paul Eggert on Sat, 20 Jan 2024 17:41:57 -0800)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=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:315167
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/315167>

> Date: Sat, 20 Jan 2024 17:41:57 -0800
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> When I built with --enable-checking this seemed to help significantly on 
> Ubuntu 23.10 x86-64 with GCC 13.2 -O2 (at least looking at the machine 
> code; I didn't benchmark). This depends on compiler and platform so it'd 
> be helpful if Stefan could try it out on his machine and see whether it 
> helps his cases' performance.

If you didn't benchmark, how did you see that these changes help
significantly the ENABLE_CHECKING build?

Thanks.