My "listen to every episode ASAP" list:
Opening Arguments
Scathing Atheist
God Awful Movies
Skepticrat
Cognative Dissonance
Skeptics with a K
Be Reasonable
Inkredulous

My backup list:
Dogma Debate
Naked Mormonism
What's the Point
Monster Talk

I have this habit of wanting to hear people talk about truth and evidence, and exploring how that goes wrong...

I can recommend Foundation Beyond Belief, at https://foundationbeyondbelief... . It is a humanist organization, so they are explicitly trying to just do good without promoting a religion.

They forward your money on to other causes (and it is clearly identified what they take as overhead, and you can reduce/increase that as you wish). They vet those causes for effectiveness. Every quarter they change who they donate money to, and you can adjust where your money goes within those groups.

They have an easy system to setup monthly payments, as well as giving you your end of year tax form, so it's painless to spread out your donation over time.

Line Replaceable Unit, meaning it's an unit that can be swapped out quickly.

Somehow I don't think that term really applies here...

Http://www.manager-tools.com

A life saver for me. Their very first podcast was on this exact topic (and, for that matter, every subsequent podcast). I can't recommend them highly enough.

Wow... 69,642 is a low UID?

I *am* a god!

I actually thought that the fact that you forget it is 3D was a big plus.... they don't make it in your face, but it is a nice addition to the film. Eventually you just don't notice it anymore, but it still makes a difference.

http://www.shop3m.com/70006020948.html

Gotta love the stuff

I just went through a similiar exercise at work, to determine if TCP was a good enough protocol for a slow point to point wireless connection with a high bit error rate.

We ended up using DummyNet on FreeBSD, mostly because we happened to have a high-end FreeBSD box handy...

It's not just GCC. The bug is actually in the kernel... you can propose that GCC be extra careful not to trigger this bug, but if someone wants to make a binary that triggers it, they don't need GCC to do that.

It's a potential security hole, and an almost certain memory corruption-waiting-to-happen, and needs to get fixed in the kernel. GCC reverting to the old behaviour will, at best, prevent people from accidentally finding this.