This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug jit/64810] jit not working on armv7hl ("ld: error: /tmp/libgccjit-ZGemdr/fake.so uses VFP register arguments, /tmp/ccJFCBsE.o does not")
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 27 Jan 2015 14:27:34 +0000
- Subject: [Bug jit/64810] jit not working on armv7hl ("ld: error: /tmp/libgccjit-ZGemdr/fake.so uses VFP register arguments, /tmp/ccJFCBsE.o does not")
- Auto-submitted: auto-generated
- References: <bug-64810-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64810
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Both the compiler and libgccjit were configured with:
> --with-tune=cortex-a8 --with-arch=armv7-a --with-float=hard
> --with-fpu=vfpv3-d16 --with-abi=aapcs-linux
> on the configure command line. Perhaps some of these options are set for
> driver only (libgccjit presumably doesn't use any driver) and need to be
> passed explicitly to the compiler?
libgccjit *does* use the driver; the library runs toplev.c to generate a .s
file, then invokes the driver to turn it into a .so file. It looks like
there's some kind of mismatch between these two things.
It looks like I'm going to need to get onto armvhl hw (or qemu) to investigate
further.
Jakub: BTW, the jit testsuite does extra-verbose logging, beyond jit.log; in
particular the arguments for both of the invocations above are logged to:
gcc/testsuite/jit/*.log.txt
so if it's easy to hack up the specfile to stick these in the uuencoded logs,
that might be beneficial.