JAM indexing errors prevents compilation

[kiranshila]

As far as I (and the C compiler) can tell, the constant CORE_INFO is a single byte in some but not all cases:

mlib_devel/jasper_library/sw/jam/casper_tapcp.c

Lines 245 to 246 in 1109264

	extern const uint8_t _core_info;
	#define CORE_INFO (&_core_info)

So in lines such as

mlib_devel/jasper_library/sw/jam/casper_tapcp.c

Line 1185 in 1109264

state->ptr = (void *)(CORE_INFO - 2);

and

mlib_devel/jasper_library/sw/jam/casper_devcsl.c

Lines 7 to 8 in 1109264

	extern const uint8_t _core_info;
	#define CORE_INFO (&_core_info)

mlib_devel/jasper_library/sw/jam/casper_devcsl.c

Line 21 in 1109264

if(!CORE_INFO[0] || !CORE_INFO[1]) {

mlib_devel/jasper_library/sw/jam/casper_devcsl.c

Line 70 in 1109264

if(!CORE_INFO[0] || !CORE_INFO[1]) {

yield compiler errors that prevent the JAM software from building

[jack-h]

what Xilinx tool version are you compiling with?

[david-macmahon]

Maybe something has changed in the toolchain related to the linker? More details on how _core_info are intended to (and used to) work can be found in #9f4dd46.

[david-macmahon]

Not sure why GitHub didn't auto-link that commit hash to this:
9f4dd46

[kiranshila]

what Xilinx tool version are you compiling with?

Not sure - I think this was 2021? It was a while ago when I tried :(