New Contributor
Super ContributorASSERT is not typically a synthesizable construct so I'm surprised this ever displayed anything during a compilation in Quartus standard. It's meant for simulation only.
I do see in Quartus help that there are messages that can be displayed for ASSERT, so it's possible that the move to Pro, with a synthesis engine that more closely follows the IEEE standards which say to ignore ASSERT during synthesis, that this feature was removed. Can you provide code example(s)? That might help to see if there's an equivalent to what you're trying to do.
#iwork4intel
New ContributorDear Honored Contributor,
Sorry to say that "Beginner" is absolutely right in his demand.
"Assertions are not for synthesis" is a lame joke. The Assertion statement has always been working perfectly in Quartus Prime Std !
I suggest you refer to the Quartus Manual (see screenshot) and file this big parser bug to be corrected, as we are so many to ask.
And I'm surprised you didn't notice that it does affect Intel own IPs.
The ability for an IP to stop the compilation when something is wrong in the settings is not a gadget.
Bert
