Glibc change exposing bugs
Glibc change exposing bugs
Posted Nov 11, 2010 12:25 UTC (Thu) by NikLi (guest, #66938)In reply to: Glibc change exposing bugs by slashdot
Parent article: Glibc change exposing bugs
There is also a big advantage by doing that: hopefully gcc in some cases can detect the alignment of pointers at compile-time and use even faster variants, which is even more important.
At least we hope that the gcc devs will remain sane (inclusion of "go" frontend is scary knowing that google tends to withdraw services and software without much thought (wave, etc))...
Posted Nov 11, 2010 14:49 UTC (Thu)
by nix (subscriber, #2304)
[Link]
Go is not just 'google': Go (in GCC) is Ian Lance Taylor, who is a very-long-standing GCC hacker who doesn't have a record for abandonware (hell, he put out a new release of Taylor UUCP not too long ago, and how old is *that*?)
Glibc change exposing bugs