01-06-2021 02:37 PM - edited 01-06-2021 03:09 PM
Compared to v2020.1, generating an xclbin in v2020.2 is significantly slower. Is this known to be the case?
After what was already an excruciatingly long time, I am now stuck at "Phase 4.1 Global Iteration 0" with Vivado pegging multiple cores of my CPUs on a dual 18-core Xeon system with 128 GB RAM.
There are lots of critical warnings too, like this one:
01-07-2021 01:55 AM
I would not expect 2020.2 to be slower than 2020.1. If you can share a test case we can have a look.
Else maybe could you at least share the log files for the same project in 2020.1 an 2020.2?
01-08-2021 08:38 AM
It's becoming increasingly difficult for me to create meaningful test cases as my application continues to grow in complexity. However, I can tell you with certainty that the Vitis "v++ --link" step took under 40 minutes in 2020.1, but it took over 1 hour and 20 minutes in 2020.2.
01-08-2021 09:31 AM
01-10-2021 09:24 PM
Possibly. I will have to re-run the 2020.1 version to make sure I have the correct logs. At this point, I have migrated to 2020.2 and have not looked back, other than than this speed issue. Let me see if I can pull something together by the end of the week, but I have bigger fish to fry at the moment.