From: Pip Cet <pipcet@protonmail.com>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: MPS: unable to build due to assertion violation in igc_dump_check_object_starts
Date: Wed, 24 Jul 2024 08:21:11 +0000 [thread overview]
Message-ID: <xuv2jb718pEMXkpsg3n76jnb6Qdsy59pTnFHK5DkCuoCXcCOVJ_uf-mlwUduHUrctqkEgYdDlVDsrvu_uwCGZmMEPopEcL_yAV4AI9X9g5k=@protonmail.com> (raw)
In-Reply-To: <87v80v6wxd.fsf@gmail.com>
On Wednesday, July 24th, 2024 at 08:01, Helmut Eller <eller.helmut@gmail.com> wrote:
> On Tue, Jul 23 2024, Pip Cet wrote:
> > I'm pretty sure it's the bignum thing, currently testing a fix.
> I think fix_wrapped_vec is also broken for 32-bit hardware:
Thanks for checking! I'm not sure I understand the problem, so please excuse the silly questions.
> First, is_aligned doesn't make any sense; client is neither a tagged
> pointer nor does it point to a header.
It points to the contents area of a struct Lisp_Vector. Since the Lisp vector header is aligned to 8 bytes, and 16 bytes in size including the MPS header, the client address also has to be aligned.
I believe the best thing to do here is to calculate the header address and assert, not check, that it is aligned. Unaligned addresses should never get here.
> Second, sizeof (struct Lisp_Vector) is 16 because the struct decl has
> GCALIGNED_STRUCT. The code should perhaps use header_size or
> offsetof (struct Lisp_Vector, content).
I'm not sure I understand. sizeof (struct Lisp_Vector), header_size, and offsetof (struct Lisp_Vector, content) are all 16.
(And, yes, that means wasting 32 bits per vector. Is that the problem?)
Pip
next prev parent reply other threads:[~2024-07-24 8:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 12:58 MPS: unable to build due to assertion violation in igc_dump_check_object_starts Eli Zaretskii
2024-07-23 14:10 ` Gerd Möllmann
2024-07-23 14:26 ` Eli Zaretskii
2024-07-23 14:40 ` Eli Zaretskii
2024-07-23 14:52 ` Gerd Möllmann
2024-07-23 15:43 ` Eli Zaretskii
2024-07-23 16:29 ` Gerd Möllmann
2024-07-23 18:00 ` Eli Zaretskii
2024-07-23 18:37 ` Eli Zaretskii
2024-07-23 18:40 ` Pip Cet
2024-07-23 18:48 ` Gerd Möllmann
2024-07-23 19:12 ` Pip Cet
2024-07-23 19:25 ` Gerd Möllmann
2024-07-23 19:30 ` Gerd Möllmann
2024-07-23 22:47 ` Pip Cet
2024-07-24 3:50 ` Gerd Möllmann
2024-07-24 11:27 ` Eli Zaretskii
2024-07-24 8:01 ` Helmut Eller
2024-07-24 8:21 ` Pip Cet [this message]
2024-07-24 8:33 ` Helmut Eller
2024-07-24 9:20 ` Pip Cet
2024-07-24 9:39 ` Helmut Eller
2024-07-24 9:54 ` Pip Cet
2024-07-24 11:40 ` Helmut Eller
2024-07-24 12:25 ` Pip Cet
2024-07-24 11:44 ` Eli Zaretskii
2024-07-23 18:50 ` Gerd Möllmann
2024-07-23 18:42 ` Gerd Möllmann
2024-07-23 18:49 ` Eli Zaretskii
2024-07-23 18:59 ` Gerd Möllmann
2024-07-23 14:42 ` Pip Cet
2024-07-23 16:28 ` Pip Cet
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='xuv2jb718pEMXkpsg3n76jnb6Qdsy59pTnFHK5DkCuoCXcCOVJ_uf-mlwUduHUrctqkEgYdDlVDsrvu_uwCGZmMEPopEcL_yAV4AI9X9g5k=@protonmail.com' \
--to=pipcet@protonmail.com \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).