rank correlation between GDP and life expectancy (child mortality would have been maybe a bit better). uses a 20 year window in both directions per year. bootstraps for 5% and 95% quantiles of the rank correlation.
there looks to be a max around 1992, and steady downhill in correlation since then.
this seems unlikely to be an artifact of the analysis, though 1992 is eerily close to 20 years from the last date. 2013 is the last year where we have at least 15 years total symmetriclaly around the given year to include in the correlation for that year.
Yes, but it can be more of a pain keeping track of pairs. In production though, this is what's done. And given a fault, the debug binary can be found in a database and used to gdb the issue given the core. You do have to limit certain online optimizations in order to have useful tracebacks.
This also requires careful tracking of prod builds and their symbol files... A kind of symbol db.
Google is made of many thousands of individuals. Some experts will be aware of all those, some won't. In my team, many didn't know about those details as they were handled by other builds teams for specific products or entire domains at once.
But since each product in some different domains had to actively enable those optimizations for themselves, they were occasionally forgotten, and I found a few in the app I worked for (but not directly on).
ICF seems like a good one to keep in the box of flags people don't know about because like everything in life it's a tradeoff and keeping that one problematic artifact under 2GiB is pretty much the only non-debatable use case for it.
Once the compiler has generated a 32-bit relative jump with an R_X86_64_PLT32 relocation, it’s too late. (A bit surprising for it to be a PLT relocation, but it does make some sense upon reflection, and the linker turns it into a direct call if you’re statically linking.) I think only RISC-V was brave enough to allow potentially size-changing linker relaxation, and incidentally they screwed it up (the bug tracker says “too late to change”, which brings me great sadness given we’re talking about a new platform).
On x86-64 it would probably be easier to point the relative call to a synthesized trampoline that does a 64-bit one, but it seems nobody has bothered thus far. You have to admit that sounds pretty painful.
It does. But maybe someone should prove (in Lean?) that the lack of flow control is sufficient.
Without a constraint that values aren’t ignored, the lack of flow control is certainly not sufficient, so trying to do this right would require defining (in Lean!) what an expression is.
https://colab.research.google.com/drive/1tstVoKkVP_8B7dTOofa...
nice plot at the bottom.
rank correlation between GDP and life expectancy (child mortality would have been maybe a bit better). uses a 20 year window in both directions per year. bootstraps for 5% and 95% quantiles of the rank correlation.
there looks to be a max around 1992, and steady downhill in correlation since then.
this seems unlikely to be an artifact of the analysis, though 1992 is eerily close to 20 years from the last date. 2013 is the last year where we have at least 15 years total symmetriclaly around the given year to include in the correlation for that year.
reply