all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>, emacs-devel@gnu.org
Subject: Re: 32-bit MinGW build with JIT
Date: Sun, 19 Aug 2018 09:24:37 -0600	[thread overview]
Message-ID: <87k1omgz0q.fsf@tromey.com> (raw)
In-Reply-To: <838t56iet0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Aug 2018 17:09:15 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli> I'm not yet sure what causes this, but since I presume that the branch
Eli> was successfully built on a 64-bit host, I suspect some snafu with
Eli> pointers that are narrower than 64-bit integers.

Thanks for trying this.  I'm very ill so I haven't been able to look
into this code.  I will when I'm able.

Also I'm about 1/4 of the way through converting it to use gcc-jit, so
we can see how well that works.

Eli> All the libjit types are "incomplete" as far as
Eli> GDB is concerned, there are no facilities to display libjit types and
Eli> values in human-readable form, C-level backtraces show ?? when a JIT
Eli> compiled function is called, etc.

I built my own libjit with debuginfo and IIRC that was good enough for
normal things.

For stack traces through JIT code, you need the gdb unwinder I wrote.
It hasn't been checked in to libjit yet:

    http://lists.gnu.org/archive/html/libjit/2018-02/msg00014.html

I only made this work for x86-64 but porting it shouldn't be too hard.

Tom



  parent reply	other threads:[~2018-08-19 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 14:09 32-bit MinGW build with JIT Eli Zaretskii
2018-08-16 17:35 ` Eli Zaretskii
2018-08-18  9:14   ` Eli Zaretskii
2018-08-19 15:24 ` Tom Tromey [this message]
2018-08-19 15:37   ` Eli Zaretskii
2018-08-19 15:50     ` Tom Tromey
2018-08-19 16:15       ` Eli Zaretskii
2018-08-27 19:52         ` Ken Brown
2018-08-28  5:25           ` Eli Zaretskii
2018-08-28 13:12             ` Ken Brown
2018-08-28 16:58               ` Eli Zaretskii
2018-08-19 17:11     ` 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=87k1omgz0q.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --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 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.