Re:Google offers free fabbing for 130nm open-source chips
by klyrs on Tuesday July 07, 2020 @09:07PM
(#23765985)
FWIW a lot of c++ developers see std:: and TODO as synonyms. OTOH, having used some of Xilinx's tool, I'd be terrified to read the internals.
[ Parent
| on HN ]
Re:Google offers free fabbing for 130nm open-source chips
by denkmoon on Wednesday July 08, 2020 @12:30AM
(#23766897)
> std:: and TODO as synonyms
What does this mean? I've only been in the C++ game for 6 years and for me if I can get something from std rather than rolling my own or pulling in another library, I'm cheering.
Re:Google offers free fabbing for 130nm open-source chips
by klyrs on Wednesday July 08, 2020 @01:33AM
(#23767157)
Yes they're wonderful to have, don't get me wrong! They're general-purpose and robust! But they're also insufficient for a lot of needs. One thing that comes up for me a lot is a lack of static-allocated structures, and sometimes there are optimizations that can be made by sacrificing certain functionality.
Re:Google offers free fabbing for 130nm open-source chips
by shaklee3 on Wednesday July 08, 2020 @12:53AM
(#23767002)
Lots of people replace STL with a faster one. See EA
Re:Google offers free fabbing for 130nm open-source chips
by CountSessine on Wednesday July 08, 2020 @06:15PM
(#23774790)
EA’s STL had more to do with custom allocators and the fact that a lot of the platforms we were developing for 10 years ago didn’t have mmap or paged memory management (or at least nothing that they wanted to expose to us lowly user-mode gamedevs).