You seem to be all for the utter and total betrayal of the "beta" soldiers, for the betterment of the "alpha" soldiers. There doesn't seem to be much else to say.

Well, there we have it! Netcraft confirms blah blah blah.

I'm trying to understand this... Are you glorifying cowards who use other people as human shields? Maybe I'm misunderstanding.

But memset is not pure in the general case where it might write to memory referenced by a global pointer or a pointer passed in to the calling function.

But it likely is inline. Especially since the code to implement it is smaller than the code to set up a call.

I know gcc has a great many declarable attributes for functions these days. Perhaps one of those was (mis-)used.

If it was really about the cost of peering (as opposed to rent seeking), Comcast could have accepted Netflix offer of a cache server.

Sender pays has never been how it works. Netflix paid Level3 for their bandwidth and Comcast's customers paid Comcast.

When you and someone in Japan communicate over the net, do you expect a bill from NTT?

The sad part is with all of those codes they shat out, they're still missing venomous sea creatures.

We're going to need more lasers.

Here's the thing, I have already purchased bandwidth and the sites I want to contact have as well. In order for it to be fair, I and they should actually get what was paid for,

I'm not absolutely sure how it is coming to it's conclusions, but I *THINK* rather than being special treatment, it sees that memset itself only affects the allocated memory passed to it in pointers and it knows that that memory in this case is on the stack and will be freed when the calling function returns, so it concludes there are no side-effects and elides the call. In theory, casting the pointer to volatile should force the compiler to leave the call in.

Yes. The double assignment being undefined is proper because the statements are ambiguous at the semantic level. I would say the best policy is to stay far away from it. It should be considered at least a warning condition. Eliding the memset is inexcusable in a sane spec because there was no ambiguity.

There are a few ways to trick the compiler into doing the right thing, but it's a shame it has to be done that way. But given the importance, there should at least be a really_memset or a securely_memset available in hopes of giving the programmer some chance to get the proper behavior.

If you're going to complain about immigrants working on advanced aerospace technology and the Apollo project in essentially the same breath, it might be worth noting all of the German immigrants who worked on the Apollo project.

I do support the cops being recorded when on duty. I also support those recordings only being viewed when there is a citizen complaint or when facts surrounding an arrest are contested in court, and then only for the time period involved.

They should not be actively monitored by big brother.