{"push_id":1275469325,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"a45da58b41c3a5086c7001e598fecefa60ebae1b","before":"9c00c889025f1a69c4f2f9fce793aff377b35b78","commits":[{"sha":"2b93899057a4c52cf523114b582bbca48b035cb2","author":{"name":"bmeurer","email":"4e74bbcea38878a9b79972ae6059bbd5e04fe066@chromium.org"},"message":"[turbofan] Remove remaining uses of Class type from the compiler.\n\nWe (mis)used Type::Class to track stable field maps in the past. But\nthat always more or less unsupport and wrong for various reasons, mostly\nbecause the class types do not really present static information and\nthus it is possible to violate fundamental assumptions of the type\nsystem (i.e. intersecting class types and other types produces\n\"interesting\" results).\n\nNow it is possible to finally nuke the class types completely and thus\nsimplify (and ideally correctify) the type system further.\n\nNote to performance sheriff: We do expect to see some performance\nregressions from this change. This is because we do not yet have a sane\nreplacement mechanism to track known field maps and utilize them during\nLoadElimination. This will be accomplished in a follow up CL.\n\nBUG=v8:5270,v8:5267\nR=jarin@chromium.org\n\nReview-Url: https://codereview.chromium.org/2293343002\nCr-Commit-Position: refs/heads/master@{#39031}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/2b93899057a4c52cf523114b582bbca48b035cb2"},{"sha":"b98d64f909db4ae2eda9fabcbab9cf0f81cb76ac","author":{"name":"bmeurer","email":"4e74bbcea38878a9b79972ae6059bbd5e04fe066@chromium.org"},"message":"[turbofan] Extend LoadElimination to introduce TypeGuards.\n\nIf the type of a tracked field or element value is less precise than the\nadvertised type of the field or element load, then we replace the load\noperation with a TypeGuard that guards the advertised type.\n\nR=jarin@chromium.org\nBUG=v8:5267\n\nReview-Url: https://codereview.chromium.org/2295643002\nCr-Commit-Position: refs/heads/master@{#39032}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/b98d64f909db4ae2eda9fabcbab9cf0f81cb76ac"},{"sha":"a45da58b41c3a5086c7001e598fecefa60ebae1b","author":{"name":"bmeurer","email":"4e74bbcea38878a9b79972ae6059bbd5e04fe066@chromium.org"},"message":"[turbofan] Don't eliminate FinishRegion nodes.\n\nThe way we use FinishRegion for transitioning stores makes them eligible\nfor elimination by TypedOptimization, which is unintended and removes\nthe atomicity of the transitioning stores. This is a quickfix to ensure\nthat we don't remove the FinishRegion nodes during TypedOptimization;\nthe real fix is probably to have separate region operators for value\n(producing) regions (i.e. allocations) and for effect-only regions (i.e.\ntransitioning stores).\n\nR=jarin@chromium.org\nBUG=v8:5303\n\nReview-Url: https://codereview.chromium.org/2293023003\nCr-Commit-Position: refs/heads/master@{#39033}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/a45da58b41c3a5086c7001e598fecefa60ebae1b"}]}
{"actor":{"display_login":"kisg"}}