New Contributor
Occasional ContributorHelo,
I am encountering this same problem. Thanks for your solution above; I am trying it and things are at least running. How long did it take for this new error to show up (how far into the quartus build)?
I agree, none of this used to be necessary. I assume this is the result of them switching over to 20.1. I don't know if it's possible to point back at 19.4, but if you can, that might work better. Maybe. :-)
Thank you!
New ContributorHi,
The error comes up as soon as aoc hits this stage:
aoc: Compiling for FPGA. This process may take several hours to complete. Prior to performing this compile, be sure to check the reports to ensure the design will meet your performance targets. If the reports indicate performance targets are not being met, code edits may be required. Please refer to the Intel FPGA SDK for OpenCL Best Practices Guide for information on performance tuning applications for FPGAs.
This happens in a minute or so... Haven't you seen it? I'm using the 19.3 version of the compiler, by the way. The function I pointed out allows to choose the Quartus version you want.
Thank you.
Occasional ContributorOh, that's a shame that changing aoc versions doesn't help.
BTW, is your design a OneAPI design (SYCL) or an OpenCL design at heart? Mine's entirely OpenCL.
Both my builds failed last night in identical ways. I left them running after I watched them get up to at least 10 minutes wall clock time, so when I looked this morning and saw your note that your builds had failed within a minute or so, I was hopeful. However, it was not to be. I submitted these as batch jobs, so I get an error and output file. The error file says this:
WARNING: this job is dumping too much data into the standard error stream. This log is truncated.
=>> PBS: job killed: walltime 21602 exceeded limit 21600
The output file says this:
########################################################################
# Date: Wed May 6 16:05:42 PDT 2020
# Job ID: 591614.v-qsvr-1.aidevcloud
# User: u40073
# Resources: neednodes=1:fpga_compile:ppn=2,nodes=1:fpga_compile:ppn=2,walltime=06:00:00
########################################################################
WARNING: this job is dumping too much data into the standard output stream. This log is truncated.
########################################################################
# End of output for job 591614.v-qsvr-1.aidevcloud
# Date: Wed May 6 22:05:48 PDT 2020
########################################################################
That is the sum total of the output I got from either job. I checked the bin directories to which I'd directed the output, hoping there'd be compilation directories in there with logs I could look at (this supposed excessive error data), but both directories were empty.
They apparently take their log truncation pretty seriously. :-)
Please let me know if you find any solution to your compilation woes. I'll do the same.
Thank you!
New ContributorMine is a pure OpenCL design as well.
I'll post here the solution if a find any, but it seems unlikely... I hope someone from Intel can come up with a fix.
Thank you.
Occasional ContributorThings have gone from bad to worse today in the dev cloud (see https://forums.intel.com/s/question/0D50P00004fMGpxSAG/oneapi-dev-clouds-a-hot-mess-today), but I have one additional data point regarding our particular problem here:
I tried to do a hardware build of the OpenCL vector_add example. I had built this example about a month ago on the dev cloud using 19.3 or whatever version was the default at that time. It built and ran fine on the a10_pac card. Today, I set off the build (using the environment setup you suggested above) and the build ran for all six allotted hours (it normally completes in under an hour) and then exited with the exact same error and output messages I reported above. Again, the bin target directory was empty.
