From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757727Ab2DXVSd (ORCPT ); Tue, 24 Apr 2012 17:18:33 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:49623 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756379Ab2DXVSc (ORCPT ); Tue, 24 Apr 2012 17:18:32 -0400 MIME-Version: 1.0 In-Reply-To: <4F9717E6.8030506@amacapital.net> References: <20120424161039.293018424@chello.nl> <4F9717E6.8030506@amacapital.net> From: Linus Torvalds Date: Tue, 24 Apr 2012 14:18:09 -0700 X-Google-Sender-Auth: x3ZDOgET0c0e3tK939bZbharp5A Message-ID: Subject: Re: [RFC][PATCH 0/3] gcc work-around and math128 To: Andy Lutomirski Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Andrew Morton , Juri Lelli Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 24, 2012 at 2:15 PM, Andy Lutomirski wrote: > > I played with some of this stuff awhile ago, and for timekeeping, it > seemed like a 64x32->96 bit multiply followed by a right shift was > enough, and that operation is a lot faster on 32-bit architectures than > a full 64x64->128 multiply. Ack. That may sound like odd numbers, but 64x32->96 sounds sane. And I think it avoids a multiply even on 64-bit, no? Linus