Always optimize for adding properties to native objects.

Always optimize for adding properties to native objects.

R=jkummerow@chromium.org

Committed: https://crrev.com/c715098e85b93def76c0b3f54290c811dea04f01
Cr-Commit-Position: refs/heads/master@{#28003}

[Jakob Kummerow, 2015-04-22 11:17:09]

lgtm

[Yang, 2015-04-22 11:31:21]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2015-04-22 11:31:32]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1094383004/1

[commit-bot: I haz the power, 2015-04-22 12:11:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-22 13:19:32]

Patchset 1 (id:??) landed as
https://crrev.com/c715098e85b93def76c0b3f54290c811dea04f01
Cr-Commit-Position: refs/heads/master@{#28003}

[Yang, 2015-04-22 13:20:52]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1098223004/ by yangguo@chromium.org.

The reason for reverting is: GC stress failure (custom snapshot).

[Toon Verwaest, 2015-04-22 17:03:25]

verwaest@chromium.org changed reviewers:
+ verwaest@chromium.org

[Toon Verwaest, 2015-04-22 17:03:25]

What objects is this change for?

[Yang, 2015-04-23 13:59:35]

On 2015/04/22 17:03:25, Toon Verwaest wrote:
> What objects is this change for?

There are a couple of objects extended by only a few functions. By not
converting the object to slow mode before and back to fast after adding those
functions, we unnecessarily create a transition chain. For examples see
object-observe.js (last dozen of lines).