11,634 karma · joined December 13, 2011
> Normally you'd start from bytecode, build an SSA, then do a pass where you apply type information.
> With Warp, the design simplifies into stitching together a bunch of CacheIR chunks which already embed the optimization information you care about, and then compiling that.
This is what I meant by ditching most of the profiling stuff; I suppose I should have said "type inference stuff" to be more precise.
> Originally the "shared code" was emitted by a bunch of statically defined methods that emitted a fixed bit of assembly (one for each kind of stub). That became unweildy as we added more stubs, so CacheIR was designed.
I remember all too well :) I worked on the first pass at implementing megamorphic caches into the original stub generators that spit out (macro)assembly directly, before we had CacheIR. So much code duplication...
Yes. Well, that, and Firefox talks to backend services (updates, safe browsing, etc) to do its job for the user, whereas cURL doesn't.
> Do you actually find it hard to believe that the legal terms attached to cURL are entirely sufficient an that Mozilla is using different terms because Mozilla is planning to take meaningfully different actions with respect to user data?
I've known a lot of Mozilla folks for a long time, so, yes.
I don't know what the best reference to link for this would be, but look up "Warp" or "WarpMonkey" if you're interested.
[0] https://en.wikipedia.org/wiki/Category:Association_for_Compu...
https://docs.github.com/en/get-started/exploring-projects-on...
1. No Such Thing As A Fish; 2. My Brother, My Brother And Me; 3. Planet Money; 4. Revolutions; 5. 99% Invisible; 6. Stuff You Should Know; 7. The Adventure Zone; 8. This American Life; 9. Freakinomics Radio; 10. The Rest Is History
I had to scroll to #32 to find Casefile which sorta fits your criteria, except it's hosted by a dude and I think he generally discusses older cases.