pratk

7 ms·

1. 1.▲
   Rust front-end merged in GCC trunk(gcc.gnu.org)

   158 points by pratk 4y ago|130 comments
2. 2.▲
   by pratk 4y ago

   Well C does allow "copying" an array if it's wrapped inside a struct, which does not make it O(1). gcc generates calls to memcpy in assembly for copying the array.
3. 3.▲
   by pratk 4y ago

   One C idiom that I found pretty useful is Xmacros [1]. For instance, it's used extensively in GCC code-base (.def files). [1] https://www.drdobbs.com/the-new-c-x-macros/184401387
4. 4.▲
   by pratk 4y ago

   I work at a company that has been operating remotely since a decade. In our weekly syncs (or 1:1 with manager), there's little to no small talk, and the meeting gets called off if there's not much agenda. For socials, we have a mo
5. 5.▲
   by pratk 4y ago

   -fwrapv forces the compiler to handle signed overflow with 2's complement. UB essentially means the compiler is free to do anything, and with the option it chooses the wrapping behavior. See https://stackoverflow.com/qu
6. 6.▲
   by pratk 4y ago

   Also, the UB can be mitigated with -fwrapv (if desired) to handle overflowing integers with 2's complement
7. 7.▲
   by pratk 4y ago

   Well, we have defect reports in language specs too: https://www.open-std.org/jtc1/sc22/wg14/www/docs/summary.htm
8. 8.▲
   by pratk 4y ago

   Looks interesting, thanks! Just curious, any plans for supporting SIMD, similar to gcc's vector extensions ?