I've reported that this issues are still open through multiple channels after 2017.1 came out. The CRs are still marked "Fixed in 2017.1".
Those two bugs that @XilinxInc claims to have fixed in Vivado 2017.1, but didn't: Still broken in 2017.2! (CR 966939 and CR 967845)pic.twitter.com/l6zL0QmkmD
-
-
-
Both bug reports come with simple scripts that demonstrate the bugs. Both script still "work" with 2017.2. Really easy to check.
- Show replies
New conversation -
-
-
Yes, opt_design has quite a few options. See "help opt_design" on the TCL command line for more information.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If you are looking for a quick fix: Simply add the missing export for RDI_VERBOSE to rdiArgs.sh, and you can still use multithreading.pic.twitter.com/AslRDdhKuc
-
Should fix most of the other "multithreading segfaults" as well. No idea why it takes Xilinx over 6 months to add this missing export..
End of conversation
New conversation -
-
-
Well, that HUTEnv::setEnv() is calling setenv() instead of unsetenv() for a NULL argument is segfault related.. See http://svn.clifford.at/handicraft/2016/vivadosig11/README …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.