unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu,  pipcet@protonmail.com,  emacs-devel@gnu.org,
	eller.helmut@gmail.com
Subject: Re: MPS: assertion failed: header_type (h) != IGC_OBJ_FWD
Date: Tue, 16 Jul 2024 18:54:47 +0200	[thread overview]
Message-ID: <m2cyndxoo8.fsf@pro2.fritz.box> (raw)
In-Reply-To: <86v815gy67.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Jul 2024 18:21:36 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> But it's not limited to struct members. The question is similar for
>> control stacks, and anything allocated via malloc. Given an address
>> range [start, end) to scan with scan_ambig, where can references be
>> found?
>
> AFAIU, each memory block allocated by malloc is guaranteed to have the
> alignment of the largest fundamental data type on the platform.  So
> yes, 8-byte alignment is guaranteed in this case.  (See also the
> max_align_t data type introduced by C11.)

Please note that I'm not talking about the alignment of allocated
memory, but of the r4ferences contained in that memory. Anyway, I'm
following my gut right now. Let's see.




  reply	other threads:[~2024-07-16 16:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14  4:12 MPS: assertion failed: header_type (h) != IGC_OBJ_FWD Gerd Möllmann
2024-07-14  5:30 ` Pip Cet
2024-07-14  7:00   ` Gerd Möllmann
2024-07-14  7:08     ` Gerd Möllmann
2024-07-16 13:02     ` Gerd Möllmann
2024-07-16 13:38       ` Eli Zaretskii
2024-07-16 13:47         ` Gerd Möllmann
2024-07-16 14:11           ` Eli Zaretskii
2024-07-16 14:39             ` Gerd Möllmann
2024-07-16 15:21               ` Eli Zaretskii
2024-07-16 16:54                 ` Gerd Möllmann [this message]
2024-07-16 14:19           ` Helmut Eller
2024-07-16 14:48             ` Gerd Möllmann
2024-07-16 15:22               ` Eli Zaretskii
2024-07-16 16:13               ` Pip Cet
2024-07-16 16:47                 ` Gerd Möllmann
2024-07-17  7:51                 ` Andrea Corallo
2024-07-17 19:47               ` Gerd Möllmann
2024-07-18 15:08                 ` Gerd Möllmann
2024-07-18 16:05                   ` Pip Cet
2024-07-18 16:33                     ` Gerd Möllmann
2024-07-18 19:06                   ` Andrea Corallo
2024-07-18 19:33                     ` Gerd Möllmann
2024-07-19  4:38                       ` Gerd Möllmann
2024-07-23  0:36                         ` Pip Cet
2024-07-23  3:31                           ` Gerd Möllmann
2024-07-16 15:49         ` Paul Eggert

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=m2cyndxoo8.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.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).