3 ms·
Many of the tools are bleeding edge, developing new features to support a new process node at the same time as the new process node is being developed.
by ip26 7y ago
Many of the tools are bleeding edge, developing new features to support a new process node at the same time as the new process node is being developed.
- rcxdude 7y agoThis doesn't seem relevant to most of the tooling, which is not bleeding edge, and should be mature.
- gchadwick 7y agoCertainly on the simulator/synthesis side you can still encounter straight-forward bugs in SystemVerilog features that were standardized over a decade ago (or find they're not implemented at all) or even simple parsing bugs (the kinds of bugs that would be trivial to find with some decent randomised testing of the parser). Things being bleeding edge and fast evolving in certainly true for some EDA tools or parts of them but there's lots of more bread and butter stuff that never feels quite right.
- jfkebwjsbx 7y agoThat is no excuse. A lot of software out there is bleeding edge, yet costumers do not tolerate crashes.
- api 7y agoSure, that's why important software never crashes. /sarcasm
- jfkebwjsbx 7y agoAnd... it does not. Most crashes in actually important software are due to hardware/memory errors, rather than the software itself. Of course, I hope you are not referring to Windows or any day-to-day software by "important".