unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eggert@cs.ucla.edu, acm@muc.de, emacs-devel@gnu.org
Subject: Re: Excessive use of `eassert`
Date: Fri, 19 Jan 2024 18:23:06 +0200	[thread overview]
Message-ID: <83mst1uwb9.fsf@gnu.org> (raw)
In-Reply-To: <jwveded5ojx.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 19 Jan 2024 10:50:51 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Paul Eggert <eggert@cs.ucla.edu>,  Alan Mackenzie <acm@muc.de>,
>   emacs-devel@gnu.org
> Date: Fri, 19 Jan 2024 10:50:51 -0500
> 
> > since 2016.  I use an Emacs build with ENABLE_CHECKING and without
> > optimizations every day, and while it is indeed slower than the
> > production build by a factor of 3.5, it is not unbearably slow.
> 
> Same here.  I can't vouch for 3.5 specifically, but 3-4 sounds about
> right for me as well.  Tho I'll also note that (many) years ago
> the slowdown was lower, more in the 2x ballpark.

It's possible that GCC optimizes better nowadays.  Also, back then we
had macros, not inline functions that sometimes aren't inlined.

> In any case, I'm not insisting.

Neither am I.

> I already removed that assertion from
> my local branch, which is the one that affects me.  My messages was
> mostly intended to share my discovery/surprise: I always assumed that
> something like `Qnil` in the source would turn into some kind of
> constant in the machine code (possibly modulo relocation), regardless of
> ENABLE_CHECKING.

Let's see what Paul and Alan think.



  reply	other threads:[~2024-01-19 16:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 22:35 Excessive use of `eassert` Stefan Monnier
2024-01-19  7:04 ` Eli Zaretskii
2024-01-19 13:01   ` Stefan Monnier
2024-01-19 15:02     ` Eli Zaretskii
2024-01-19 15:50       ` Stefan Monnier
2024-01-19 16:23         ` Eli Zaretskii [this message]
2024-01-19 17:44           ` Stefan Monnier
2024-01-19 19:42       ` Alan Mackenzie
2024-01-19 19:56         ` Eli Zaretskii
2024-01-21  1:41         ` Paul Eggert
2024-01-21  9:57           ` Eli Zaretskii
2024-01-21 20:35             ` Paul Eggert
2024-01-21 10:59           ` Alan Mackenzie
2024-01-22  5:19             ` Paul Eggert
2024-01-22 13:07               ` Stefan Monnier
2024-01-22 14:37               ` Alan Mackenzie
2024-01-23  7:51                 ` Paul Eggert
2024-01-23 11:42                   ` Alan Mackenzie
2024-01-24  1:04                     ` Paul Eggert
2024-01-24 15:09                       ` Alan Mackenzie
2024-01-26  8:06                         ` Paul Eggert
2024-01-21 15:54           ` Stefan Monnier
2024-01-22  4:12             ` Paul Eggert
2024-01-22 13:20               ` Stefan Monnier
2024-01-23  8:15                 ` Paul Eggert
2024-01-23 17:11                   ` Stefan Monnier
2024-01-24  7:45                     ` Paul Eggert
2024-01-23 18:16                   ` Eli Zaretskii
2024-01-23 19:50                     ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mst1uwb9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).