Have the profiler load the correct registers on x64.
authordeanm@chromium.org <deanm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 6 May 2009 11:19:50 +0000 (11:19 +0000)
committerdeanm@chromium.org <deanm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 6 May 2009 11:19:50 +0000 (11:19 +0000)
commit5f4322f77f91d284e4a777c45f6c1fad4232954b
tree6314e7a7afbbd0630c519cf4b162d2907fcf2bd9
parentb32d7d2e679d376600b4ff691a4dd5a185ba37aa
Have the profiler load the correct registers on x64.

This is still not correct, since internally they are kept as an int.
Use our new V8_HOST_ARCH macros for detecting the host processor.

Review URL: http://codereview.chromium.org/109025

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1879 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/platform-linux.cc