Can anyone repro this Vivado bug? Tested on 2016.3 and 2017.2 with the same results. https://pastebin.com/raw/AaSZqQ37 . Seems OK under ISE 14.7
-
The zero byte terminates the string because C strings are used as intermediate storage. Vivado preserves the original length, yosys not.
So it's not exactly the same way wrong, but afaics both do the wrong thing here.
-
-
Interesting. So you think Vivado sees the N-byte string, null terminates, then puts the contents into the last (N-1) with the MS byte zero?
-
That is consistent with what I've been seeing.
- 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.