From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Subject: Adding extra fields to float_block and cons_block?
Date: Wed, 22 Sep 2021 20:54:10 +0800 [thread overview]
Message-ID: <875yuszs7h.fsf@yahoo.com> (raw)
In-Reply-To: 875yuszs7h.fsf.ref@yahoo.com
I tried adding an extra array of bits_words to cons_block and
float_block, in alloc.c, defined as follows:
bits_word gc_pushed_to_stack_ps[1 + FLOAT_BLOCK_SIZE / BITS_PER_BITS_WORD];
But now Emacs crashes with:
alloc.c:1252: Emacs fatal error: assertion failed: nbytes <= BLOCK_BYTES
Fatal error 6: Aborted
I can't seem to figure out the hairy mess surrounding that code, and I'd
appreciate it if someone could explain the proper procedure for adding
extra fields to those two structs. Thanks.
next parent reply other threads:[~2021-09-22 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875yuszs7h.fsf.ref@yahoo.com>
2021-09-22 12:54 ` Po Lu [this message]
2021-09-22 18:19 ` Adding extra fields to float_block and cons_block? Stefan Monnier
2021-09-23 0:07 ` Po Lu
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=875yuszs7h.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--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).