I've just posted another @XilinxInc Vivado bug found with VlogHammer: http://www.clifford.at/yosys/vloghammer_bugs/issue_058_vivado.html …
Unfortunately I don't have a way of creating Xilinx SRs anymore, so I have no means of reporting this bug. Anyone here feels like reporting it?
-
Show this thread
-
Replying to @oe1cxw @XilinxInc
There are no SR possible for 7 series or earlier. To submit a SR the bug must be replicated on UltraScale, then we could submit SR for you
1 reply 0 retweets 1 like -
Replying to @AnttiBrain @XilinxInc
All of those bugs are for the HDL front-end. Nothing in any of those 4 descriptions mentions any specific series of devices. What gives you the impression that those reports are specific to 7 series?
1 reply 0 retweets 0 likes -
Replying to @oe1cxw @XilinxInc
I did mean that Xilinx only accept SR for projects using UltraScale, so to report a generic issue one still needd to say the problem is related to active project with ultrascale device
1 reply 0 retweets 0 likes -
Replying to @AnttiBrain @XilinxInc
I still don't quite understand what you want me to do. Just click "new project" in Vivado, add the Verilog file, and click synthesis. The two cases that hang will hang, for the other ones, click open synth design and view schematic to see the constant outputs. Or simply this:pic.twitter.com/Fx8c2kI6Gg
1 reply 0 retweets 1 like -
If by "SR" U mean "service request", then this thread demonstrates extra vividly, how stupid the situation is with the closed source EDA software. Come on, a competent guy like the
@oe1cxw putting@XilinxInc 2 its Bug findings description Tweet SHOULD BE ENOUGH to report bugs.1 reply 1 retweet 0 likes -
Replying to @martin_vahi @oe1cxw and
The megacorporations have nice "chicks" or otherwise beauties at their reception desks, full time paid Public Relations/propaganda employees on their payroll, and yet they can't hire some tech student to pick up bug reports from social media hints. That's a matter of attitude!
1 reply 1 retweet 2 likes -
Yes, SR = Service Request. Usually you have to debate with a support engineer for a week or so until you have convinced them that there's a bug in the software. Then they will create a CR (Change Request) internally.
1 reply 1 retweet 3 likes -
Replying to @oe1cxw @martin_vahi and
Maybe 3-18 months later the CR gets closed with "fixed in <release ~6 months away>". But sometimes the release comes out and the bug is still there. Then you have to reopen the SR and back to start. It can take years to get a bug fixed.
2 replies 1 retweet 2 likes -
Replying to @oe1cxw @martin_vahi and
Don't get mad at these guys. For anything that is tooling for safety critical stuff certification and strict quality control is needed. That sometimes means, that a bug report does not get priority. Hangs are nasty but they don't directly lead to failures.
1 reply 0 retweets 0 likes
(1) I am not mad at anyone. I'm just stating facts. (2) Two of the four bugs we are discussing here are cases where Vivado silently produces incorrect synthesis results, as are most of the bugs I found with VlogHammer. One of those two I first reported in 2014.
-
-
If that's the case with the FPGAs, then that's probably also the case with digital logic based circuits, CPUs, etc. that are "hardwired" at semiconductor foundry and that are used at car ABS breaks, heart pace makers, things that have a label "safety critical" in sales talk.
1 reply 0 retweets 0 likes -
Replying to @martin_vahi @oe1cxw and
My practical takeaway from this thread is that I should really try to think of algorithm development with some kind of watchdog induced reset in mind. Not just to withstand power failures, but in the context of being efficient/fast at booting @ regular intervals. Bast booting.
0 replies 1 retweet 0 likes
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.