Use initializer_lists for static WTF::HashSets.

Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code and
a smaller binary, plus it lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.

Committed: https://crrev.com/499ab26b15f221bbd217f068720bc9fe9b2e6923
Cr-Commit-Position: refs/heads/master@{#405043}

[esprehn, 2016-07-12 03:20:19]

The CQ bit was checked by esprehn@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-12 03:21:01]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-12 04:54:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-12 04:54:19]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[esprehn, 2016-07-12 19:10:23]

esprehn@chromium.org changed reviewers:
+ haraken@chromium.org, jbroman@chromium.org

[esprehn, 2016-07-12 19:11:27]

Description was changed from

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in both prettier code
and a smaller binary.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

to

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat in the static tables.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

[esprehn, 2016-07-12 19:11:37]

Description was changed from

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat in the static tables.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

to

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat in the static sets.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

[esprehn, 2016-07-12 19:13:55]

Description was changed from

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat in the static sets.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

to

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

[jbroman, 2016-07-12 19:22:25]

lgtm \o/

[haraken, 2016-07-13 00:09:07]

LGTM. Great.

[esprehn, 2016-07-13 00:39:08]

The CQ bit was checked by esprehn@chromium.org

[esprehn, 2016-07-13 00:39:46]

Description was changed from

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code a
smaller binary, and lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

to

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code and
a smaller binary, plus it lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

[commit-bot: I haz the power, 2016-07-13 00:42:30]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-13 02:57:24]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-13 02:57:26]

Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[esprehn, 2016-07-13 03:57:39]

The CQ bit was checked by esprehn@chromium.org

[commit-bot: I haz the power, 2016-07-13 03:58:16]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-13 05:22:24]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-13 05:25:02]

Description was changed from

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code and
a smaller binary, plus it lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.
==========

to

==========
Use initializer_lists for static WTF::HashSets.

HashSet::add() inlines a lot of code at the call site for performance,
but this causes binary bloat when setting up large static hash sets.

Lets use initializer lists instead, this results in prettier code and
a smaller binary, plus it lets the hash set reserve the right capacity
immediately avoiding bloat and rehashing.

In a shared library Release build I see:
- libmodules.dylib gets 15.7k smaller.
- libwebcore_shared.dylib gets 30.9k smaller.
- libblink_platform.dylib gets 1k smaller.

This also makes the object files smaller, for example
modules.DatabaseAuthorizer.o is reduced from 592kb to 466kb for a
reduction in size of 126kb.

Committed: https://crrev.com/499ab26b15f221bbd217f068720bc9fe9b2e6923
Cr-Commit-Position: refs/heads/master@{#405043}
==========

[commit-bot: I haz the power, 2016-07-13 05:25:04]

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