GEP is not of right type for indices! [Vivado HLS 2014.4, 2015.2, synthesis internal error]

Question

[Vivado HLS 2014.4, 2015.2, synthesis internal error]
Hello,
I am randomly getting an error "GEP is not of right type for indices". (check the included files)
Some time it is presented as internal error sometimes GEP error appears.
If i reset vivado HLS error disappears dissapear and if i run synthesis again it works.
But problem is not the interface itself. Design is top big to share (and quite unusual with very specific needs). I would like to make a sample, but i don't know what error means and I don't know what causing the issue.
Did anyone met this error?
Does anyone have any idea what is causing the problem? (If i find out, I will make a samle. )
explanations for types in sources:
descrFifo_r and descrFifo_w are instances of Multififo and  all arrays are defined with
#pragma HLS ARRAY_PARTITION variable=xx complete dim=1
multififo is implementation of multichannel  fifo it to same block ram in one cycle only one channel can write and only one can make read request and only one can collect delayed data
It is tested and works in HW
 

Answer 1

Hello,
Thank you debrajr you gave me hope that that issue is fixable.
I removed associated ARRAY_PARTITION directives, it did not help.
I used script to remove all ARRAY_PARTITION directives and error seems to be the same.
So i tried to remove all the pragma and result is still same.
(If i compile my code, it runs with 0 Valgrind errors/warnings, so there is not pointer mismatch or any other problem of this kind, from c++ point of view, everythink seems to be OK)
But I found line, which causes the bug.
From some reason sometimes reading from MultiFifo<...>.bm_rd.dout fail with this error.
Today I found that sometimes I accidentaly read from very different output interface (not even connected with Multififo<>), I have fixed this section I did not met any synthesis errors for long time, that could mean that the issue was this impossible access on this interface.
Is there some way to let Vivado HLS write out all internal problems? Somethink like debugmod?
Is there way to write for example top 10 critical paths ? It would be really helpfull.
It tooks me nearly 3 days to debug this and this project is small (just ~1500 lines of code)....
Problem fixed for now.