Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:What's wrong with GCC? (Score 1) 711

by Xpilot (#39987165) Attached to: FreeBSD 10 To Use Clang Compiler, Deprecate GCC
You know how BSD advocacy folks like to tell you they "don't like politics"? It's kind of like the story in the Onion about that guy who keeps telling people he doesn't own a television and how much more fulfilling his life is, even when no one asked. BSD advocacy folks are _just as political_ as the GPL crowd. The reason to use GCC isn't performance, it's the only free compiler that supports a multitude of target architectures. And that's very very useful. Dropping utility over licensing kind of smacks of the thing GNU is accused of when BSD advocacy folks get all snooty about technical superiority.

Comment: Fixing is easier said than done (Score 5, Insightful) 396

by Xpilot (#12565390) Attached to: Hyper-Threading, Linus Torvalds vs. Colin Percival
The kernel developers don't seem to agree on the right way to fix this, whether at the kernel level or in userspace. However, it may affect the performance of the kernel if it's done in kernelspace, and it is impractical to have everyone rewrite their userland software, as someone else pointed out. The "patch" which is available for FreeBSD to fix this problem only disables hyperthreading and does not provide a real fix.

"An organization dries up if you don't challenge it with growth." -- Mark Shepherd, former President and CEO of Texas Instruments

Working...