Description:
The issue is caused by some differences in the behavior of the Verific and Synplify language parsers related to the handling of the escape characters in the instance name.
Solution:
This is not yet fixed by Synplify Pro and no timeline yet provided by the third-party tool.
Currently, there is a manual workaround so the user can resume work on the project. If the user removes the \ characters from the Synplify-generated .ldc file, then the constraints will be accepted by the database.
For users using the command line/tcl flow for radiant, this should be done in a few simple steps:
1. Run the normal flow up to synplify or synpwrap if the lattice-supplied wrapper is used.
2. Find the Synplify Output .ldc file (the .ldc file will be named <project name>_<implementation_name>.ldc')
3. Remove all the '\' characters from the constraints that are inside the '{}' brackets (a simple search and replace should do).
4. Run postsyn command, should not see any constraints dropped
5. Run the rest of the flow as normal
After this process, the user should see that no constraints are dropped.
For the GUI flow it would be as follows:
1. Run the project through synthesis.
2. Find the Synplify Output .ldc file, this should be located in the project implementation directory.
(the ldc file will be named <project name>_<implementation_name>.ldc')
Note that the succeeding screenshots are based on an example project only.