On 05/08/2015 07:41 AM, David Malcolm wrote:
On Thu, 2015-05-07 at 17:30 -0700, Aldy Hernandez wrote:
Hi folks.
I have divided the patches into 10 pieces. The patches are
interdependent and cannot be applied independently. I am merely
dividing them up to aid the relevant reviewers.
As I've mentioned elsewhere, the patchset as posted has been
bootstrapped and GCC tested on:
x86_64-unknown-linux-gnu
powerpc-ibm-aix7.1.2.0
powerpc64-unknown-linux-gnu
aarch64-unknown-linux-gnu
I have also GDB tested the patchset on x86_64-linux.
Thanks for your help in this ordeal.
Aldy: did you test the jit with this? Specifically, is gdb still able
to step through the generated code/inspect values?
etc; see e.g:
https://gcc.gnu.org/onlinedocs/jit/intro/tutorial04.html#single-stepping-through-the-generated-code
Sadly the jit testsuite doesn't yet automatically verify that sane
debuginfo is generated; I've only ever hand-tested that (this is PR
jit/64196).
If the jit doesn't have a testsuite that runs from "make check", then no.
Alternatively, I guess I can try your branch if that's easier (exactly
which should I test?)
I will not be upset if you can test :). Just checkout the branch
(origin/aldyh/debug-early) and build/use it normally. There should not
be any differences to mainline. If there are, it's a bug that must be
fixed.
Let me know, and thanks!
Aldy
