Forum Discussion
OpenCL Compiler Local Memory Address Space Splitter fails
- 7 years ago
Thank you for your reply, AKert. It is great to hear that my report is of some value. Meanwhile, I have found that the issue seems to be caused by reading from global memory and writing to an Intel FPGA channel in a single statement. When replacing
UTL_WRITE_CH(ch_1, data1[j]); UTL_WRITE_CH(ch_2, buf_d2[i]);with (make sure to use the actual types)
const my_type1 temp1 data1[j] UTL_WRITE_CH(ch_1, temp1); const my_type2 temp2 buf_d2[i] UTL_WRITE_CH(ch_2, temp2);the error goes away. It may or may not be related to also using char (8 bits) buffers.
Intel engineer here. The problem you have encountered is an assertion in the compiler code, which as you suspected (usually) indicates a bug in the tool, not a problem with the input. I can't see anything obviously wrong with your OpenCL code that would trigger this.
I've opened a ticket in the engineering system to have this looked at, with a cross-link to this post.
Thanks for taking the time to post this issue! This is valuable feedback; the fact that it crashes in multiple releases suggests a corner case we failed to consider. It's extremely helpful to have a minimal non-working example to debug from.