01707c7106
Always use CpuFeaturesImpliedByCompiler() when selecting CPU features. This checks both for CAN_USE_ARMV7_INSTRUCTIONS and CAN_USE_VFP_INSTRUCTIONS and for GCC preprocessor symbols. This will support using the CAN_USE_XXX for a simulator build used for generating a snapshot followed by a crosscompile using -march= and -mfpu= for selecting the (minimal) target device CPU features. The snapshot will use instructions based on the CAN_USE_XXX whereas the target will at least use features based on both CAN_USE_XXX and -march= and -mfpu=, but will try runtime CPU feature detection a well looking for somethis better. Remove the compiler based CPU feature detection from the OS::CpuFeaturesImpliedByPlatform() as it did not belong there. Also was already in the CpuFeaturesImpliedByCompiler(). Add the variable 'v8_can_use_vfp_instructions' to the GYP file which can be used to turn on CAN_USE_VFP_INSTRUCTIONS when building V8. I did not add any -mfpu= cflags for this, as there are several options here (e.g. vfp and neon). R=erik.corry@gmail.com, karlklose@chromium.org BUG=none TEST=none Review URL: http://codereview.chromium.org//6904164 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7754 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
36 lines
389 B
Plaintext
36 lines
389 B
Plaintext
*.a
|
|
*.exe
|
|
*.lib
|
|
*.log
|
|
*.map
|
|
*.mk
|
|
*.ncb
|
|
*.pyc
|
|
*.scons*
|
|
*.suo
|
|
*.user
|
|
*.xcodeproj
|
|
*.idb
|
|
*.pdb
|
|
#*#
|
|
*~
|
|
.cpplint-cache
|
|
d8
|
|
d8_g
|
|
shell
|
|
shell_g
|
|
/build/gyp
|
|
/obj/
|
|
/test/es5conform/data/
|
|
/test/mozilla/data/
|
|
/test/sputnik/sputniktests/
|
|
/test/test262/data/
|
|
/tools/oom_dump/oom_dump
|
|
/tools/oom_dump/oom_dump.o
|
|
/tools/visual_studio/Debug
|
|
/tools/visual_studio/Release
|
|
/xcodebuild/
|
|
TAGS
|
|
Makefile
|
|
*.Makefile
|