Use numeric_limits<double>::infinity() for conversions of Time::Max().

Infinity has mostly the same semantics of
numeric_limits<double>::max(), which was being used before, but with
the added bonus that numbers added and subtracted to it shouldn't
change it.

R=ajwong@chromium.org,jar@chromium.org,mkwst@chromium.org
BUG=None

Review URL: https://codereview.chromium.org/163493004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253455 0039d316-1c4b-4281-b951-d872f2087c98
NaCl SDK: don't prune PNaCl biased bitcode from the NaCl SDK build.

Some NaCl users want to use the PNaCl toolchain to build native NaCl
applications that use C++11 and compiler intrinsics. This currently
isn't feasible with the GCC toolchain, and PNaCl doesn't currently offer
all the intrinsics these users want (effectively non-portable inline
assembly). For such a build to work users need libraries that are built
with bitcode biased for their architecture: the front-end knows that it
will target x86-32/x86-64/ARM/MIPS up front and compiles the code
accordingly (e.g. with SSE or NEON support, with certain function
signatures and calling-conventions that follow the platforms'
convention).

This CL increases the size of the NaCl SDK.

The NaCl-side of this CL (building more biased bitcode) is:
  https://codereview.chromium.org/164553005

R= binji@chromium.org, sbc@chromium.org, noelallen@chromium.org, jvoung@chromium.org
TEST=none
BUG=none

Review URL: https://codereview.chromium.org/176923005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253456 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 253455
SVN changes up to revision 253456