|
| 1 | +2014-12-16 Matthew Hanson <matthew_hanson@apple.com> |
| 2 | + |
| 3 | + Merge r176399. rdar://problem/19267545 |
| 4 | + |
| 5 | + 2014-11-19 Mark Lam <mark.lam@apple.com> |
| 6 | + |
| 7 | + WTFCrashWithSecurityImplication under SpeculativeJIT::compile() when loading a page from theblaze.com. |
| 8 | + <https://webkit.org/b/137642> |
| 9 | + |
| 10 | + Reviewed by Filip Pizlo. |
| 11 | + |
| 12 | + In the DFG, we have a ConstantFolding phase that occurs after all LocalCSE |
| 13 | + phases have already transpired. Hence, Identity nodes introduced in the |
| 14 | + ConstantFolding phase will be left in the node graph. Subsequently, the |
| 15 | + DFG code generator asserts that CSE phases have consumed all Identity nodes. |
| 16 | + This turns out to not be true. Hence, the crash. We fix this by teaching |
| 17 | + the DFG code generator to emit code for Identity nodes. |
| 18 | + |
| 19 | + Unlike the DFG, the FTL does not have this issue. That is because the FTL |
| 20 | + plan has GlobalCSE phases that come after ConstantFolding and any other |
| 21 | + phases that can generate Identity nodes. Hence, for the FTL, it is true that |
| 22 | + CSE will consume all Identity nodes, and the code generator should not see any |
| 23 | + Identity nodes. |
| 24 | + |
| 25 | + * dfg/DFGSpeculativeJIT32_64.cpp: |
| 26 | + (JSC::DFG::SpeculativeJIT::compile): |
| 27 | + * dfg/DFGSpeculativeJIT64.cpp: |
| 28 | + (JSC::DFG::SpeculativeJIT::compile): |
| 29 | + |
| 30 | +2014-12-10 Matthew Hanson <matthew_hanson@apple.com> |
| 31 | + |
| 32 | + Merge r176972. <rdar://problem/19196762> |
| 33 | + |
| 34 | + 2014-12-08 Mark Lam <mark.lam@apple.com> |
| 35 | + |
| 36 | + CFA wrongly assumes that a speculation for SlowPutArrayStorageShape disallows ArrayStorageShape arrays. |
| 37 | + <https://webkit.org/b/139327> |
| 38 | + |
| 39 | + Reviewed by Michael Saboff. |
| 40 | + |
| 41 | + The code generator and runtime slow paths expects otherwise. This patch fixes |
| 42 | + CFA to match the code generator's expectation. |
| 43 | + |
| 44 | + * dfg/DFGArrayMode.h: |
| 45 | + (JSC::DFG::ArrayMode::arrayModesThatPassFiltering): |
| 46 | + (JSC::DFG::ArrayMode::arrayModesWithIndexingShapes): |
| 47 | + |
| 48 | + |
| 49 | +2014-12-10 Matthew Hanson <matthew_hanson@apple.com> |
| 50 | + |
| 51 | + Merge r175653. <rdar://problem/19196762> |
| 52 | + |
| 53 | + 2014-11-05 Mark Lam <mark.lam@apple.com> |
| 54 | + |
| 55 | + PutById inline caches should have a store barrier when it triggers a structure transition. |
| 56 | + <https://webkit.org/b/138441> |
| 57 | + |
| 58 | + Reviewed by Geoffrey Garen. |
| 59 | + |
| 60 | + After r174025, we no longer insert DFG store barriers when the payload of a |
| 61 | + PutById operation is not a cell. However, this can lead to a crash when we have |
| 62 | + PutById inline cache code transitioning the structure and re-allocating the |
| 63 | + butterfly of an old gen object. The lack of a store barrier in that inline |
| 64 | + cache results in the old gen object not being noticed during an eden GC scan. |
| 65 | + As a result, its newly allocated butterfly will not be kept alive, which leads |
| 66 | + to a stale butterfly pointer and, eventually, a crash. |
| 67 | + |
| 68 | + It is also possible that the new structure can be collected by the eden GC if |
| 69 | + (at GC time): |
| 70 | + 1. It is in the eden gen. |
| 71 | + 2. The inline cache that installed it has been evicted. |
| 72 | + 3. There are no live eden gen objects referring to it. |
| 73 | + |
| 74 | + The chances of this should be more rare than the butterfly re-allocation, but |
| 75 | + it is still possible. Hence, the fix is to always add a store barrier if the |
| 76 | + inline caches performs a structure transition. |
| 77 | + |
| 78 | + * jit/Repatch.cpp: |
| 79 | + (JSC::emitPutTransitionStub): |
| 80 | + - Added store barrier code based on SpeculativeJIT::storeToWriteBarrierBuffer()'s |
| 81 | + implementation. |
| 82 | + |
| 83 | + |
| 84 | +2014-12-10 Matthew Hanson <matthew_hanson@apple.com> |
| 85 | + |
| 86 | + Merge r175593. <rdar://problem/19196762> |
| 87 | + |
| 88 | + 2014-11-04 Mark Lam <mark.lam@apple.com> |
| 89 | + |
| 90 | + Rename checkMarkByte() to jumpIfIsRememberedOrInEden(). |
| 91 | + <https://webkit.org/b/138369> |
| 92 | + |
| 93 | + Reviewed by Geoffrey Garen. |
| 94 | + |
| 95 | + Write barriers are needed for GC Eden collections so that we can scan pointers |
| 96 | + pointing from old generation objects to eden generation objects. The barrier |
| 97 | + currently checks the mark byte in a cell to see if we should skip adding the |
| 98 | + cell to the GC remembered set. The addition should be skipped if: |
| 99 | + |
| 100 | + 1. The cell is in the young generation. It has no old to eden pointers by |
| 101 | + definition. |
| 102 | + 2. The cell is already in the remembered set. While it is ok to add the cell |
| 103 | + to the GC remembered set more than once, it would be redundant. Hence, |
| 104 | + we skip this as an optimization to avoid doing unnecessary work. |
| 105 | + |
| 106 | + The barrier currently names this check as checkMarkByte(). We should rename it |
| 107 | + to jumpIfIsRememberedOrInEden() to be clearer about its intent. |
| 108 | + |
| 109 | + Similarly, Jump results of this check are currently named |
| 110 | + ownerNotMarkedOrAlreadyRemembered. This can be misinterpreted as the owner is |
| 111 | + not marked or not already remembered. We should rename it to |
| 112 | + ownerIsRememberedOrInEden which is clearer about the intent of the |
| 113 | + check. What we are really checking for is that the cell is in the eden gen, |
| 114 | + which is implied by it being "not marked". |
| 115 | + |
| 116 | + * dfg/DFGOSRExitCompilerCommon.cpp: |
| 117 | + (JSC::DFG::osrWriteBarrier): |
| 118 | + * dfg/DFGSpeculativeJIT.cpp: |
| 119 | + (JSC::DFG::SpeculativeJIT::writeBarrier): |
| 120 | + * dfg/DFGSpeculativeJIT32_64.cpp: |
| 121 | + (JSC::DFG::SpeculativeJIT::writeBarrier): |
| 122 | + * dfg/DFGSpeculativeJIT64.cpp: |
| 123 | + (JSC::DFG::SpeculativeJIT::writeBarrier): |
| 124 | + * jit/AssemblyHelpers.h: |
| 125 | + (JSC::AssemblyHelpers::jumpIfIsRememberedOrInEden): |
| 126 | + (JSC::AssemblyHelpers::checkMarkByte): Deleted. |
| 127 | + * jit/JITPropertyAccess.cpp: |
| 128 | + (JSC::JIT::emitWriteBarrier): |
| 129 | + * llint/LowLevelInterpreter.asm: |
| 130 | + * llint/LowLevelInterpreter32_64.asm: |
| 131 | + * llint/LowLevelInterpreter64.asm: |
| 132 | + * runtime/JSCell.h: |
| 133 | + |
| 134 | + |
| 135 | +2014-12-10 Matthew Hanson <matthew_hanson@apple.com> |
| 136 | + |
| 137 | + Merge r175243. <rdar://problem/19196762> |
| 138 | + |
| 139 | + 2014-10-27 Mark Lam <mark.lam@apple.com> |
| 140 | + |
| 141 | + Crash when attempting to perform array iteration on a non-array with numeric keys not initialized. |
| 142 | + <https://webkit.org/b/137814> |
| 143 | + |
| 144 | + Reviewed by Geoffrey Garen. |
| 145 | + |
| 146 | + The arrayIteratorNextThunkGenerator() thunk was not checking for the case where |
| 147 | + the butterfly may be NULL. This was the source of the crash, and is now fixed. |
| 148 | + |
| 149 | + In addition, it is also not checking for the case where a property named "length" |
| 150 | + may have been set on the iterated object. The thunk only checks the butterfly's |
| 151 | + publicLength for its iteration operation. Array objects will work fine with this |
| 152 | + because it always updates its butterfly's publicLength when its length changes. |
| 153 | + In the case of iterable non-Array objects, the "length" property will require a |
| 154 | + look up outside of the scope of this thunk. The fix is simply to limit the fast |
| 155 | + case checks in this thunk to Array objects. |
| 156 | + |
| 157 | + * jit/ThunkGenerators.cpp: |
| 158 | + (JSC::arrayIteratorNextThunkGenerator): |
| 159 | + |
| 160 | + |
| 161 | +2014-12-04 Dana Burkart <dburkart@apple.com> |
| 162 | + |
| 163 | + Merge r176803. <rdar://problem/19034499> |
| 164 | + |
| 165 | + 2014-12-04 Oliver Hunt <oliver@apple.com> |
| 166 | + |
| 167 | + Serialization of MapData object provides unsafe access to internal types |
| 168 | + https://bugs.webkit.org/show_bug.cgi?id=138653 |
| 169 | + |
| 170 | + Reviewed by Geoffrey Garen. |
| 171 | + |
| 172 | + Converting these ASSERTs into RELEASE_ASSERTs, as it is now obvious |
| 173 | + that despite trying hard to be safe in all cases it's simply to easy |
| 174 | + to use an iterator in an unsafe state. |
| 175 | + |
| 176 | + * runtime/MapData.h: |
| 177 | + (JSC::MapData::const_iterator::key): |
| 178 | + (JSC::MapData::const_iterator::value): |
| 179 | + |
| 180 | + |
| 181 | +2014-11-05 Matthew Hanson <matthew_hanson@apple.com> |
| 182 | + |
| 183 | + Merge r175629. <rdar://problem/18883540> |
| 184 | + |
| 185 | + 2014-11-05 Alexey Proskuryakov <ap@apple.com> |
| 186 | + |
| 187 | + Incorrect sandbox_check in RemoteInspector.mm |
| 188 | + https://bugs.webkit.org/show_bug.cgi?id=138408 |
| 189 | + |
| 190 | + Reviewed by Joseph Pecoraro. |
| 191 | + |
| 192 | + * inspector/remote/RemoteInspector.mm: |
| 193 | + (Inspector::canAccessWebInspectorMachPort): |
| 194 | + |
| 195 | + |
| 196 | +2014-10-21 Dana Burkart <dburkart@apple.com> |
| 197 | + |
| 198 | + Merge r173238 |
| 199 | + |
| 200 | + 2014-09-03 Joseph Pecoraro <pecoraro@apple.com> |
| 201 | + |
| 202 | + Avoid warning if a process does not have access to com.apple.webinspector |
| 203 | + https://bugs.webkit.org/show_bug.cgi?id=136473 |
| 204 | + |
| 205 | + Reviewed by Alexey Proskuryakov. |
| 206 | + |
| 207 | + Pre-check for access to the mach port to avoid emitting warnings |
| 208 | + in syslog for processes that do not have access. |
| 209 | + |
| 210 | + * inspector/remote/RemoteInspector.mm: |
| 211 | + (Inspector::canAccessWebInspectorMachPort): |
| 212 | + (Inspector::RemoteInspector::shared): |
| 213 | + |
1 | 214 | 2014-08-21 Matthew Hanson <matthew_hanson@apple.com> |
2 | 215 |
|
3 | 216 | Merge r172707. <rdar://problem/18043281> |
|
0 commit comments