 Paul Leathers
|
8271639b91
Installation of the monomorphic guard type check should only happen at the original type check that guards the property access requiring monomorphism, as indicated by non-availability of the checked type.
|
il y a 10 ans |
|
Paul Leathers
|
67a4f6b27d
My previous fix to monomorphic type checks had a subtle mistake. To handle the case where a downstream store adds a property, I grabbed the store's cached initial type to use as the guard type at the monomorphic check. But in some cases, the type we checked upstream is the final type, not the initial one. One-line fix for that.
|
il y a 10 ans |
|
Paul Leathers
|
9b49b23fa6
With equivalent obj type spec on by default, certain operations still require monomorphic type checks. We've handled this in the dead store pass by locating any equivalent type check that protects an operation that requires a specific type and changing it to use a monomorphic check. But because of the vagaries of inline cache sharing, the operation that does the check may not appear to be monomorphic. Deal with this by having the dead store pass indicate the required type on the checking instruction.
|
il y a 10 ans |
 Jianchun Xu
|
8567cfe6c1
update all references to use correct CamelCase file names
|
il y a 10 ans |
|
Jianchun Xu
|
47eab483b9
change top-level dir Lib back to lib
|
il y a 10 ans |
|
Jianchun Xu
|
4e05cc2969
rename /lib/ files to CamelCase
|
il y a 10 ans |
 Rajat Dua
|
24429701bf
[MERGE #275] Bug with lossy int type spec
|
il y a 10 ans |
|
Rajat Dua
|
3546d31aac
Bug with lossy int type spec
|
il y a 10 ans |
 Josh Soref
|
2b765347f6
Fix various spelling errors.
|
il y a 10 ans |
 ChakraBot
|
5d8406741f
Initial commit
|
il y a 10 ans |
