3 ms·
I don't know, to me this is a bit like taking two c programs that print "hello world" and "goodbye world", looking at the assembly that is compiled then remarki
by qppo 6y ago
I don't know, to me this is a bit like taking two c programs that print "hello world" and "goodbye world", looking at the assembly that is compiled then remarking "pretty sad and very unmaintainable."
Point being, maintain the code generator and not the generated code.
- ptx 6y agoRight. But here the generated code is checked into the source tree and the code generator is kept proprietary, which is why it's sad and unmaintainable.
- unionpivo 6y agoCode generator probably runs of their verilog/hdl source of the chips. It probably relies (or is build on top of) on proprietary EDA tools. Without open sourcing their chips, it would probably be useless. Even if you work for chip maker, that is what you usually get from hardware guys, so we are probably getting the same as AMD own driver programmers. \s Welcome to wonderful world of driver development at majority of hardware houses \s
- ptx 6y agoThey could still separate the extraction of the data (keeping it proprietary) from the code generation. The latter could work off of the extracted data kept in a more sensible format.