|
|
Subscribe / Log in / New account

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

Having seen all sorts of crazy memcpies using MMX (glibc, DirectFB, kernel, etc, etc) and having tried to benchmark them, observing huge amounts of noise in the experinemtns, I have come to the conclusion that the best memcpy one can use is gcc's __builtin_memcpy.

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))...


to post comments

Glibc change exposing bugs

Posted Nov 11, 2010 14:49 UTC (Thu) by nix (subscriber, #2304) [Link]

The worst that will happen to go is that it suffers the fate of the CHILL frontend (nobody uses it, nobody remembers it exists, it's removed many years after introduction).

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*?)


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds