libgccjit: Add gcc_jit_context_new_array_type_unsigned_long

[antoyo]

ML link: https://gcc.gnu.org/pipermail/jit/2024q1/001842.html

• Change the type from unsigned long to uint64_t?

gcc/jit/ChangeLog:

* docs/topics/compatibility.rst (LIBGCCJIT_ABI_28): New ABI tag.
* docs/topics/types.rst: Document gcc_jit_context_new_array_type_unsigned_long.
* jit-playback.cc (new_array_type): Change num_elements type to unsigned long.
* jit-playback.h (new_array_type): Change num_elements type to unsigned long.
* jit-recording.cc (recording::context::new_array_type): Change num_elements type to unsigned long. (recording::array_type::make_debug_string): Use unsigned long format. (recording::array_type::write_reproducer): Switch to gcc_jit_context_new_array_type_unsigned_long.
* jit-recording.h (class array_type): Change num_elements type to unsigned long. (new_array_type): Change num_elements type to unsigned long. (num_elements): Change return type to unsigned long.
* libgccjit.cc (gcc_jit_context_new_array_type_unsigned_long): New function.
* libgccjit.h (gcc_jit_context_new_array_type_unsigned_long): New function.
* libgccjit.map: New function.

gcc/testsuite/ChangeLog:

* jit.dg/all-non-failing-tests.h: Add test-arrays-unsigned-long.c.
* jit.dg/test-arrays-unsigned-long.c: New test.

[antoyo]

@davidmalcolm: I'm a bit concerned about using unsigned long.
Would it be OK if I change the type to uint64_t?
I could rename the function to gcc_jit_context_new_array_type_u64.

[davidmalcolm]

@davidmalcolm: I'm a bit concerned about using unsigned long. Would it be OK if I change the type to uint64_t? I could rename the function to gcc_jit_context_new_array_type_u64.

@antoyo: Yes, unsigned long might not be big enough. My gut feeling is to use size_t rather than uint64_t since that's what's used in the C world, but maybe that could cause issues with rustc?

[antoyo]

@antoyo: Yes, unsigned long might not be big enough. My gut feeling is to use size_t rather than uint64_t since that's what's used in the C world, but maybe that could cause issues with rustc?

size_t would be 32-bits on 32-bits platform. Using uint64_t would be 64-bits on all platforms, which would allow rustc_codegen_gcc to work more easily on 32-bit platforms.