From 8a3bd712ad9f96b712d71414a049977a4aaad37e Mon Sep 17 00:00:00 2001 From: "ricow@chromium.org" Date: Fri, 14 Jan 2011 11:54:38 +0000 Subject: [PATCH] Fix win64 build by using int instead of size_t for position in StringBuilder Review URL: http://codereview.chromium.org/6353002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6313 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 --- src/x64/lithium-codegen-x64.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/x64/lithium-codegen-x64.cc b/src/x64/lithium-codegen-x64.cc index eb21b98..44a4053 100644 --- a/src/x64/lithium-codegen-x64.cc +++ b/src/x64/lithium-codegen-x64.cc @@ -83,7 +83,7 @@ void LCodeGen::Comment(const char* format, ...) { // Copy the string before recording it in the assembler to avoid // issues when the stack allocated buffer goes out of scope. - size_t length = builder.position(); + int length = builder.position(); Vector copy = Vector::New(length + 1); memcpy(copy.start(), builder.Finalize(), copy.length()); masm()->RecordComment(copy.start()); -- 2.7.4