unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 09:54:11 +0000	[thread overview]
Message-ID: <hTbo-J4EqUhNSeVMbfGAZzYCHM--zd3m7XXkgSgqGL5kSjHg5tJNmugB1RF2-9dLMDR_yEFctmQ2BCNv1LFpH8jmcgComAa7k1ofSXXppQk=@protonmail.com> (raw)
In-Reply-To: <878qxr6seb.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

On Wednesday, July 24th, 2024 at 09:39, Helmut Eller <eller.helmut@gmail.com> wrote:
> On Wed, Jul 24 2024, Pip Cet wrote:
> 
> > Is alignof(struct Lisp_Vector) == 4 for you?
> 
> No, it's 8. Because of the GCALIGNED_STRUCT attribute.

Thanks for letting me know.  Is this in gdb or lldb?  lldb shows me alignof(struct Lisp_Vector) == 4 on a similar Debian system, which looks wrong to me.  I've fixed things on that system for now (it was building without mps, because that requires -pthread in the CFLAGS to link on that machine...)

Can you try the attached patch?

Pip

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-mps-aligned.patch --]
[-- Type: text/x-patch; name=0001-mps-aligned.patch, Size: 904 bytes --]

diff --git a/src/lisp.h b/src/lisp.h
index 8a1b1acf5f0..d4331b3a4ff 100644
--- a/src/lisp.h
+++ b/src/lisp.h
@@ -45,7 +45,7 @@ #define EMACS_LISP_H
 INLINE_HEADER_BEGIN
 
 #ifdef HAVE_MPS
-union gc_header { uint64_t v; };
+union gc_header;
 extern void gc_maybe_quit (void);
 extern bool gc_signal_handler_can_run (int);
 #else
@@ -335,6 +335,7 @@ #define GCALIGNED_UNION_MEMBER char alignas (GCALIGNMENT) gcaligned;
 #endif
 #define GCALIGNED(type) (alignof (type) % GCALIGNMENT == 0)
 
+union gc_header { uint64_t v; GCALIGNED_UNION_MEMBER };
 /* Lisp_Word is a scalar word suitable for holding a tagged pointer or
    integer.  Usually it is a pointer to a deliberately-incomplete type
    'struct Lisp_X'.  However, it is EMACS_INT when Lisp_Objects and
@@ -6335,3 +6336,4 @@ define_error (Lisp_Object name, const char *message, Lisp_Object parent);
 INLINE_HEADER_END
 
 #endif /* EMACS_LISP_H */
+

  reply	other threads:[~2024-07-24  9:54 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
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 [this message]
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='hTbo-J4EqUhNSeVMbfGAZzYCHM--zd3m7XXkgSgqGL5kSjHg5tJNmugB1RF2-9dLMDR_yEFctmQ2BCNv1LFpH8jmcgComAa7k1ofSXXppQk=@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).