Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 # Copyright 2012 the V8 project authors. All rights reserved. | 1 # Copyright 2012 the V8 project authors. All rights reserved. |
| 2 # Redistribution and use in source and binary forms, with or without | 2 # Redistribution and use in source and binary forms, with or without |
| 3 # modification, are permitted provided that the following conditions are | 3 # modification, are permitted provided that the following conditions are |
| 4 # met: | 4 # met: |
| 5 # | 5 # |
| 6 # * Redistributions of source code must retain the above copyright | 6 # * Redistributions of source code must retain the above copyright |
| 7 # notice, this list of conditions and the following disclaimer. | 7 # notice, this list of conditions and the following disclaimer. |
| 8 # * Redistributions in binary form must reproduce the above | 8 # * Redistributions in binary form must reproduce the above |
| 9 # copyright notice, this list of conditions and the following | 9 # copyright notice, this list of conditions and the following |
| 10 # disclaimer in the documentation and/or other materials provided | 10 # disclaimer in the documentation and/or other materials provided |
| (...skipping 30 matching lines...) Expand all Loading... | |
| 41 # accesses. The default value of 'default' will try to determine the correct | 41 # accesses. The default value of 'default' will try to determine the correct |
| 42 # setting. Note that for Intel architectures (ia32 and x64) unaligned memory | 42 # setting. Note that for Intel architectures (ia32 and x64) unaligned memory |
| 43 # access is allowed for all CPUs. | 43 # access is allowed for all CPUs. |
| 44 'v8_can_use_unaligned_accesses%': 'default', | 44 'v8_can_use_unaligned_accesses%': 'default', |
| 45 | 45 |
| 46 # Setting 'v8_can_use_vfp_instructions' to 'true' will enable use of ARM VFP | 46 # Setting 'v8_can_use_vfp_instructions' to 'true' will enable use of ARM VFP |
| 47 # instructions in the V8 generated code. VFP instructions will be enabled | 47 # instructions in the V8 generated code. VFP instructions will be enabled |
| 48 # both for the snapshot and for the ARM target. Leaving the default value | 48 # both for the snapshot and for the ARM target. Leaving the default value |
| 49 # of 'false' will avoid VFP instructions in the snapshot and use CPU feature | 49 # of 'false' will avoid VFP instructions in the snapshot and use CPU feature |
| 50 # probing when running on the target. | 50 # probing when running on the target. |
| 51 'v8_can_use_vfp_instructions%': 'false', | 51 'v8_can_use_vfp2_instructions%': 'false', |
| 52 'v8_can_use_vfp3_instructions%': 'false', | |
| 52 | 53 |
| 53 # Similar to vfp but on MIPS. | 54 # Similar to vfp but on MIPS. |
| 54 'v8_can_use_fpu_instructions%': 'true', | 55 'v8_can_use_fpu_instructions%': 'true', |
| 55 | 56 |
| 56 # Setting v8_use_arm_eabi_hardfloat to true will turn on V8 support for ARM | 57 # Setting v8_use_arm_eabi_hardfloat to true will turn on V8 support for ARM |
| 57 # EABI calling convention where double arguments are passed in VFP | 58 # EABI calling convention where double arguments are passed in VFP |
| 58 # registers. Note that the GCC flag '-mfloat-abi=hard' should be used as | 59 # registers. Note that the GCC flag '-mfloat-abi=hard' should be used as |
| 59 # well when compiling for the ARM target. | 60 # well when compiling for the ARM target. |
| 60 'v8_use_arm_eabi_hardfloat%': 'false', | 61 'v8_use_arm_eabi_hardfloat%': 'false', |
| 61 | 62 |
| (...skipping 63 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 125 [ 'v8_can_use_unaligned_accesses=="true"', { | 126 [ 'v8_can_use_unaligned_accesses=="true"', { |
| 126 'defines': [ | 127 'defines': [ |
| 127 'CAN_USE_UNALIGNED_ACCESSES=1', | 128 'CAN_USE_UNALIGNED_ACCESSES=1', |
| 128 ], | 129 ], |
| 129 }], | 130 }], |
| 130 [ 'v8_can_use_unaligned_accesses=="false"', { | 131 [ 'v8_can_use_unaligned_accesses=="false"', { |
| 131 'defines': [ | 132 'defines': [ |
| 132 'CAN_USE_UNALIGNED_ACCESSES=0', | 133 'CAN_USE_UNALIGNED_ACCESSES=0', |
| 133 ], | 134 ], |
| 134 }], | 135 }], |
| 135 [ 'v8_can_use_vfp_instructions=="true"', { | 136 [ 'v8_can_use_vfp2_instructions=="true"', { |
| 136 'defines': [ | 137 'defines': [ |
| 137 'CAN_USE_VFP_INSTRUCTIONS', | 138 'CAN_USE_VFP2_INSTRUCTIONS', |
| 139 ], | |
| 140 }], | |
| 141 [ 'v8_can_use_vfp3_instructions=="true"', { | |
| 142 'defines': [ | |
| 143 'CAN_USE_VFP3_INSTRUCTIONS', | |
| 138 ], | 144 ], |
| 139 }], | 145 }], |
| 140 [ 'v8_use_arm_eabi_hardfloat=="true"', { | 146 [ 'v8_use_arm_eabi_hardfloat=="true"', { |
| 141 'defines': [ | 147 'defines': [ |
| 142 'USE_EABI_HARDFLOAT=1', | 148 'USE_EABI_HARDFLOAT=1', |
| 143 'CAN_USE_VFP_INSTRUCTIONS', | 149 'CAN_USE_VFP_INSTRUCTIONS', |
|
Adam Malcontenti-Wilson
2012/08/13 13:57:52
Should this be CAN_USE_VFP2_INSTRUCTIONS instead?
| |
| 144 ], | 150 ], |
| 145 'target_conditions': [ | 151 'target_conditions': [ |
| 146 ['_toolset=="target"', { | 152 ['_toolset=="target"', { |
| 147 'cflags': ['-mfloat-abi=hard',], | 153 'cflags': ['-mfloat-abi=hard',], |
| 148 }], | 154 }], |
| 149 ], | 155 ], |
| 150 }, { | 156 }, { |
| 151 'defines': [ | 157 'defines': [ |
| 152 'USE_EABI_HARDFLOAT=0', | 158 'USE_EABI_HARDFLOAT=0', |
| 153 ], | 159 ], |
| (...skipping 241 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 395 'OptimizeReferences': '2', | 401 'OptimizeReferences': '2', |
| 396 'EnableCOMDATFolding': '2', | 402 'EnableCOMDATFolding': '2', |
| 397 }, | 403 }, |
| 398 }, | 404 }, |
| 399 }], # OS=="win" | 405 }], # OS=="win" |
| 400 ], # conditions | 406 ], # conditions |
| 401 }, # Release | 407 }, # Release |
| 402 }, # configurations | 408 }, # configurations |
| 403 }, # target_defaults | 409 }, # target_defaults |
| 404 } | 410 } |
| OLD | NEW |