From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Re: 32-bit MinGW build with JIT
Date: Sun, 19 Aug 2018 18:37:06 +0300 [thread overview]
Message-ID: <83y3d2e5b1.fsf@gnu.org> (raw)
In-Reply-To: <87k1omgz0q.fsf@tromey.com> (message from Tom Tromey on Sun, 19 Aug 2018 09:24:37 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, emacs-devel@gnu.org
> Date: Sun, 19 Aug 2018 09:24:37 -0600
>
> >>>>> "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.
Sorry to hear you are ill, and hoping you will get well soon.
> Also I'm about 1/4 of the way through converting it to use gcc-jit, so
> we can see how well that works.
Does that mean any further effort on the libjit branch is a waste of
time? Also, it isn't clear to me whether gcc-jit works on non-ELF
platforms.
> I only made this work for x86-64 but porting it shouldn't be too hard.
OK, thanks.
next prev parent reply other threads:[~2018-08-19 15:37 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
2018-08-19 15:37 ` Eli Zaretskii [this message]
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
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=83y3d2e5b1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.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).