[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 32-bit MinGW build with JIT
From: |
Tom Tromey |
Subject: |
Re: 32-bit MinGW build with JIT |
Date: |
Sun, 19 Aug 2018 09:24:37 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) |
>>>>> "Eli" == Eli Zaretskii <address@hidden> 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
- 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/16
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/16
- Re: 32-bit MinGW build with JIT,
Tom Tromey <=
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/19
- Re: 32-bit MinGW build with JIT, Tom Tromey, 2018/08/19
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/19
- Re: 32-bit MinGW build with JIT, Ken Brown, 2018/08/27
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/28
- Re: 32-bit MinGW build with JIT, Ken Brown, 2018/08/28
- Re: 32-bit MinGW build with JIT, Eli Zaretskii, 2018/08/28
- Re: 32-bit MinGW build with JIT, Paul Eggert, 2018/08/19