cliffbean

17 ms·

121.
by cliffbean 14y ago
A charitable way to read this site is to use it as a way of talking about current trends. For example, they say "Male and female salaries are reaching parity" in 2067. Who knows what'll happen, but it's a novel way of talking about just how
122.
by cliffbean 14y ago
Volunteer's Dilemma and the Nash Bargaining Game have more complex equilbiria, so they're not quite as good if you're looking for an introduction to game theory. Stag Hunt is basically a game about whether the players know they are in such
123.
by cliffbean 15y ago
Also note that this restriction is in C itself. This is how restrict is defined in the C standard. It's not specific to GCC or any other compiler.
124.
by cliffbean 15y ago
Yes, the author is wrong there; restrict is valid and useful in that memcpy example. It is true though that restrict doesn't solve all of C's aliasing problems though. For example: #include <stdlib.h> struct array_3d {
125.
by cliffbean 15y ago
This sounds like an excellent occasion for the GCC maintainers to consider how revision control software has progressed in the last 25 years, and to re-evaluate the utility of the ChangeLog file; a manually maintained an "undo list" for all
126.
by cliffbean 15y ago
There are two sides of Nash's work. One is the actual math, which can be evaluated without considering the credibility of the author. The other is Nash's attempt to use it to describe the real world, which necessarily involves assumptions a
127.
by cliffbean 15y ago
I read a lot of font blog posts and find them impressive, yet ultimately unhelpful. They discuss similarities and differences with other fonts in extraordinary detail. They show images of individual glyphs enlarged beyond practicality and
128.
by cliffbean 15y ago
Recent versions of GCC do, in fact, have improved error messages. For example, GCC 4.6 fixed a problem that the post I was replying to mentioned, where a missing semicolon after a struct definition would cause GCC to elicit an error message
129.
by cliffbean 15y ago
It is useful to keep in mind a common confusion. Apple and various BSD's stopped updating GCC around version 4.2, the last GPLv2 version, which is approximately 4 years old now. For people who only develop on those platforms, this is what "
130.
by cliffbean 15y ago
The article says "monotonic", not "monophonic". The paragraph discusses pure tones and overtones.
131.
by cliffbean 15y ago
Both compilers in that 2004 paper were hardware vendor compilers, which are often heavily tuned for SPEC CPU2000. Also, both were tested with cross-translation-unit optimizations enabled; inlining in key places can make many pointer aliasin
132.
by cliffbean 15y ago
This has always bothered me. In what's typically called a 13th chord, the 11th is almost always omitted because it either clashes, or it changes the chord into something completely different. Stacking 3rds doesn't actually explain how jazz
133.
by cliffbean 15y ago
It's depressing to me that NaCl people frequently emphasize the "great piles of existing code" out there, and how "the biggest deal is that there are all these existing code bases", and how well they'll run on NaCl. I'd feel better about Na
134.
by cliffbean 15y ago
In src/liboslexec/llvm_instance.cpp, OSL uses a custom list of 13 LLVM optimizer passes (plus implicit passes pulled in as dependencies) -- less than what Clang uses at -O2 for C, but still a fair amount. Then it runs the full LLVM "-O2" ba
135.
by cliffbean 15y ago
LLVM itself knows almost nothing about GPU-specific architectural features. Emitting PTX from LLVM, for example, is mostly just a translation from one compiler IR to another compiler IR.