jwakely

9 ms·

1. 1.▲
   by jwakely 7mo ago

   It's a valid concern, and one that was raised on reddit a few times too. But if you're building an open and fair model, I hope you're not just sucking up the entire web and training it on endless stolen data, DoS'ing ope
2. 2.▲
   by jwakely 9y ago

   > Look at GCC's attitude to plugins or good error messages. Which is? A patch isn't necessary for it to be fixed, but a bug report generally is. A blog post linking to unofficial copies of documentation from 2004 doesn't c
3. 3.▲
   by jwakely 9y ago

   It's not a known issue, but GLIBCPP_FORCE_NEW has had no effect on libstdc++ code for more than a decade, so I wonder which prehistoric version you're using. Even the modern GLIBCXX_FORCE_NEW doesn't do anything for the defau
4. 4.▲
   by jwakely 9y ago

   Facts and up-to-date documentation, how novel.
5. 5.▲
   by jwakely 9y ago

   By default libstdc++ stopped using the pooling allocator in 2005: https://gcc.gnu.org/r106665 That's one year after the ancient, bitrotted, unofficial copy of the libstdc++ documentation that the blog post links to, bu
6. 6.▲
   by jwakely 9y ago

   That's a different library.
7. 7.▲
   by jwakely 9y ago

   The pooling behaviour of the libstdc++ std::allocator was only the default from 2004 until late 2005, so it went away more than a decade ago.
8. 8.▲
   by jwakely 9y ago

   GCC's std::allocator also doesn't do that (not for at least a decade, IIRC). It's a non-default allocator, which nobody is forced to use. It's entirely optional. The default std::allocator just uses new/delete.