Add V8 bug reference

kgryte · kgryte · commit 5596f4a639f6 · 2016-10-29T02:13:28.000-07:00
diff --git a/TODO.md b/TODO.md
@@ -1186,7 +1186,7 @@
 
 236. [travis-deploy-example](https://github.com/bcoe/travis-deploy-example)
 
-237. test-tools, test-tools-cov mk recipe
+237. [reserved words](http://www.javascripter.net/faq/reserved.htm) and [reserved words](https://mathiasbynens.be/notes/reserved-keywords) and [keywords](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar)
 
 238. a branch (based on `master`) which every month is run against every single Node version since `0.10.0` (may want a separate Jenkins server for this)
 
diff --git a/docs/references/bib.bib b/docs/references/bib.bib
@@ -718,3 +718,11 @@ @book{devroye:1986
 	url = {http://www.nrbook.com/devroye/},
 	year = {1986},
 }
+
+@misc{v8:3006,
+	abstract = {In Mac Chrome 33.0.1706.0 canary, Math.cos(Math.pow(2,120)) returns 0.47796506772457525. In Chromium ToT from today, after a V8 roll with the new sin/cos implementation using table lookup and interpolation, this now returns 0. The true value evaluated to full precision is closer to -0.925879. This also causes a test regression in webaudio that uses sin. This is highly unexpected that the new implementation causes a sine wave saved to a 16-bit wav file to produce different values.},
+	keywords = {math, trig, trigonometry, native, standard, chrome, chromium, v8, bug},
+	title = {{Inaccurate sin/cos values}},
+	url = {https://bugs.chromium.org/p/v8/issues/detail?id=3006},
+	year = {2013}
+}
