summaryrefslogtreecommitdiffstats
path: root/build/win
diff options
context:
space:
mode:
authorscottmg@chromium.org <scottmg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-03-04 19:01:12 +0000
committerscottmg@chromium.org <scottmg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-03-04 19:01:12 +0000
commitad062b1f1ab9f1175da716839f18645e43a660f8 (patch)
treed29fd03c33f2283904be5e826a068a36d2e3aba9 /build/win
parentab1d51fa6ec15804c38ae2df07d356bfffb0abbf (diff)
downloadchromium_src-ad062b1f1ab9f1175da716839f18645e43a660f8.zip
chromium_src-ad062b1f1ab9f1175da716839f18645e43a660f8.tar.gz
chromium_src-ad062b1f1ab9f1175da716839f18645e43a660f8.tar.bz2
Add ftol workaround for VS2013
The .obj was taken from https://connect.microsoft.com/VisualStudio/feedback/details/808199 offered as a workaround by Microsoft. This fixes the floating point stack going unbalanced. This is fixed in Update 2, and can be removed once that's rolled out. R=cpu@chromium.org, jam@chromium.org BUG=348525 Review URL: https://codereview.chromium.org/186333002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@254792 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/win')
-rw-r--r--build/win/ftol3.objbin0 -> 8246 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/build/win/ftol3.obj b/build/win/ftol3.obj
new file mode 100644
index 0000000..dc9d9ed
--- /dev/null
+++ b/build/win/ftol3.obj
Binary files differ