Sure hope so. Still using 2016.4 due to bugs introduced in 2017.1.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You mean 6GB buggabytes
-
Helpful Vivado bug of the day -> tcmalloc: large alloc 1073741824 bytes == 0x728734000 @ 0x7f0716fda63f 0x7f06ef54317c -> repeat N times
End of conversation
New conversation -
-
-
Just as an example: I'm adding this missing export to every version of Vivado since 2016.4. This fixes a segfault ! http://svn.clifford.at/handicraft/2016/vivadosig11 …pic.twitter.com/nHlh20vpSZ
-
CR for this is 966939. So *reporting* isn't the issue in this case. They just don't fix this crap!
End of conversation
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.