chrome/browser should build on the x86_64 architecture

chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm

Index: chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm
diff --git a/chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm b/chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm
index 5f93ecb4a9c40d0b35b4c4bc6aa6285c0dba6d18..e932096ccaf87139e447a09eab3b2e1e2306b14e 100644
--- a/chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm
+++ b/chrome/browser/ui/cocoa/extensions/browser_actions_controller.mm
@@ -559,7 +559,8 @@ class ExtensionServiceObserverBridge : public content::NotificationObserver,
     }
     CGFloat intersectionWidth =
         NSWidth(NSIntersectionRect([containerView_ bounds], buttonFrame));
-    CGFloat alpha = std::max(0.0f, intersectionWidth / NSWidth(buttonFrame));
+    CGFloat alpha = std::max(static_cast<CGFloat>(0.0f),

[Mark Mentovai, 2012/08/20 13:25:58]

“0.0” means “zero as a double,” whereas “0.0f” means “zero as a float,” or
“static_cast<float>(0.0).” CGFloat will now be either a float or a double. When
it’s a double and you write “static_cast<CGFloat>(0.0f),” you’re effectively
saying “take 0.0, cast it to a float, and then cast it to a double.”

You should change these from 0.0f to 0.0.

This is in line with Chrome’s other uses of CGFloat literal values which just
use doubles (no f), such as the ones a few lines above.

+                             intersectionWidth / NSWidth(buttonFrame));
     [button setAlphaValue:alpha];
     [button setNeedsDisplay:YES];
   }