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
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".
-
-
Both bug reports come with simple scripts that demonstrate the bugs. Both script still "work" with 2017.2. Really easy to check.
-
I have no idea why
@XilinxInc thinks that they fixed those issues, they do not reply to my inquiries. Seems like they simply don't care.. - Show replies
New conversation -
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.