all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@protonmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Andrea Corallo <acorallo@gnu.org>,
	Helmut Eller <eller.helmut@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
	emacs-devel@gnu.org
Subject: Re: MPS: assertion failed: header_type (h) != IGC_OBJ_FWD
Date: Tue, 23 Jul 2024 00:36:09 +0000	[thread overview]
Message-ID: <-QjTMdYbNwCUDNk0Q5XFZR2kQ0_8DHRu3A-n1Rr1_mUBhg4inwpUb3jL0lp2J1VvJcUkIQRB5v1Zy4oNePJ7V9ixJ3l91CCrb3awC_146VM=@protonmail.com> (raw)
In-Reply-To: <m2plrakndj.fsf@pro2.fritz.box>

On Friday, July 19th, 2024 at 04:38, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> Gerd Möllmann gerd.moellmann@gmail.com writes:
> 
> > Andrea Corallo acorallo@gnu.org writes:
> > 
> > > > Let's see how long igc survives this time :-).
> > > 
> > > Hi Gerd,
> > > 
> > > if you want to use '__builtin_unwind_init' be aware that this GCC bug
> > > I've found sometime ago [1] might make the builtin ineffective. It
> > > might not effect your generated code but in case you need you can see
> > > how we work it around in 'flush_stack_call_func'.
> > > 
> > > Regards
> > 
> > Thanks, that could become important at some point on platforms other
> > than macOS. AFAIK, one cannot build Emacs with GCC on newer versions of
> > macOS because the SDK is incompatible with GCC, so GCC is out of the
> > picture.
> > 
> > I haven't heard yet of anyone else having problems of the sort I have
> > here on macOS on other platforms. But maybe that comes up later.
> 
> 
> It didn't help, and no more ideas at the moment :-(.

Can you try compiling with -fno-omit-frame-pointer? I just spent entirely too much time tracing down a bug in my build to a missing option (of the same name) to x86_64 gcc. The frame pointer is stored in a mangled format by setjmp() on both darwin and glibc systems, and that caused weird problems (and since gcc generates different code with and without "-g", I had to do that without proper debugger support...)

Anyway, I think both architectures "allow" using the frame pointer register, so we're probably going to have to enforce that option, which will limit us to clang and gcc compilers unless someone figures out the configure magic...

Pip



  reply	other threads:[~2024-07-23  0:36 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='-QjTMdYbNwCUDNk0Q5XFZR2kQ0_8DHRu3A-n1Rr1_mUBhg4inwpUb3jL0lp2J1VvJcUkIQRB5v1Zy4oNePJ7V9ixJ3l91CCrb3awC_146VM=@protonmail.com' \
    --to=pipcet@protonmail.com \
    --cc=acorallo@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.