From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Opportunistic garbage collection
Date: Thu, 25 Apr 2019 20:15:48 -0400 [thread overview]
Message-ID: <jwvwojh7mj7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ffa3ed50-fc82-0c9a-29c3-e71a48f04385@cs.ucla.edu> (Paul Eggert's message of "Thu, 25 Apr 2019 15:14:16 -0700")
> And since that's signed integer multiplication, it can overflow with
> undefined behavior.
Ah, right, so it's not really the size but the sign: it should be
EMACS_UINT fact = XFIXNAT (factor);
-- Stefan
prev parent reply other threads:[~2019-04-26 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 20:54 Opportunistic garbage collection Stefan Monnier
2019-04-25 0:17 ` Paul Eggert
2019-04-25 6:27 ` Eli Zaretskii
2019-04-25 12:49 ` Stefan Monnier
2019-04-25 18:18 ` Stefan Monnier
2019-04-25 22:14 ` Paul Eggert
2019-04-26 0:15 ` Stefan Monnier [this message]
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=jwvwojh7mj7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).