aboutsummaryrefslogtreecommitdiffhomepage
path: root/include/config
diff options
context:
space:
mode:
authorGravatar reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81>2012-06-11 21:21:26 +0000
committerGravatar reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81>2012-06-11 21:21:26 +0000
commit7886ad3de1aa523d5c71f1fa9f355dfcb2412d1d (patch)
tree592ef48bd8dbfbdfe72fa5721fe5527fc9442d9b /include/config
parenta0116d541d6fee722cc159b99de6867c9ee379a5 (diff)
remove SK_CAN_USE_FLOAT (deprecated)
git-svn-id: http://skia.googlecode.com/svn/trunk@4232 2bbb7eff-a529-9590-31e7-b0007b416f81
Diffstat (limited to 'include/config')
-rw-r--r--include/config/SkUserConfig.h7
1 files changed, 0 insertions, 7 deletions
diff --git a/include/config/SkUserConfig.h b/include/config/SkUserConfig.h
index 9fdbd0a367..e7f781d733 100644
--- a/include/config/SkUserConfig.h
+++ b/include/config/SkUserConfig.h
@@ -45,13 +45,6 @@
//#define SK_SCALAR_IS_FIXED
-/* Somewhat independent of how SkScalar is implemented, Skia also wants to know
- if it can use floats at all. Naturally, if SK_SCALAR_IS_FLOAT is defined,
- SK_CAN_USE_FLOAT must be too; but if scalars are fixed, SK_CAN_USE_FLOAT
- can go either way.
- */
-//#define SK_CAN_USE_FLOAT
-
/* For some performance-critical scalar operations, skia will optionally work
around the standard float operators if it knows that the CPU does not have
native support for floats. If your environment uses software floating point,