On 3/2/23 09:25, Alex Bennée wrote:
Instead of building gdb syscalls for every target only build what
really matters, 64 or 32 bit support.
Since the *only* usage of target_ulong is in the va_list for gdb_do_syscall, and as that
passes on to printf, we could just adjust the interface to
On 3/2/23 13:21, Richard Henderson wrote:
On 3/2/23 09:25, Alex Bennée wrote:
-# These have to built to the target ABI
-specific_ss.add(files('syscalls.c'))
+# These have to built to the target ABI but are otherwise target
+# independent
+gdb32_ss = ss.source_set()
+gdb64_ss = ss.source_set()
+
On 3/2/23 09:25, Alex Bennée wrote:
-# These have to built to the target ABI
-specific_ss.add(files('syscalls.c'))
+# These have to built to the target ABI but are otherwise target
+# independent
+gdb32_ss = ss.source_set()
+gdb64_ss = ss.source_set()
+
+gdb32_ss.add(files('syscalls.c'))
Instead of building gdb syscalls for every target only build what
really matters, 64 or 32 bit support.
[AJB: Any clues or hints, I get a double linking compilation error:
FAILED: qemu-system-aarch64
c++ -m64 -mcx16 @qemu-system-aarch64.rsp
/usr/bin/ld: gdbstub/libgdb64.fa.p/syscalls.c.o: in
