more potential JSC armv7 points of concern

[stefanpenner]

• apple needs to fix it

i would consider these high risk:

• https://github.com/emberjs/ember.js/blob/f9aa3f4eb656ab22994e91e738698e4a8d377f61/packages/ember-metal/lib/events.js
• https://github.com/emberjs/ember.js/blob/f9aa3f4eb656ab22994e91e738698e4a8d377f61/packages/ember-metal/lib/dependent_keys.js

• ember.js/packages/ember-metal/lib/mixin.js

  Line 148 in a1e9072

  property = o_create(property);

• ember.js/packages/ember-metal/lib/utils.js

  Lines 306 to 309 in 3eb83a2

  	ret = o_create(ret);
  	ret.descs = o_create(ret.descs);
  	ret.watching = o_create(ret.watching);
  	ret.cache = {};

• ember.js/packages/ember-metal/lib/events.js

  Line 51 in f9aa3f4

  function actionsFor(obj, eventName) {

---

i would consider these low risk:

the following are likely not a problem, as these creating a null prototype (still often use). I would likely prefer we wait for these ones to cause issues in the wild..

• ember.js/packages/ember-metal/lib/map.js

  Line 42 in fc26db2

  }

• ember.js/packages/ember-metal/lib/streams/stream.js

  Line 27 in fc26db2

  this.children = create(null);

• ember.js/packages/ember-views/lib/system/render_buffer.js

  Line 58 in fc26db2

  this.seen = create(null);

cc @rwjblue

[rwjblue]

#9442 should fix the high risk items above.

[stefanpenner]

@rwjblue we could transform this issue into that meta-tracking issue you wanted.

[rwjblue]

@stefanpenner - Sounds good to me.