From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262583AbUBYByO (ORCPT ); Tue, 24 Feb 2004 20:54:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262587AbUBYByL (ORCPT ); Tue, 24 Feb 2004 20:54:11 -0500 Received: from uslink-66.173.43-133.uslink.net ([66.173.43.133]:59010 "EHLO dingdong.cryptoapps.com") by vger.kernel.org with ESMTP id S262581AbUBYBwx (ORCPT ); Tue, 24 Feb 2004 20:52:53 -0500 Date: Tue, 24 Feb 2004 17:52:51 -0800 From: Chris Wedgwood To: "Nakajima, Jun" Cc: Pavel Machek , Linus Torvalds , Adrian Bunk , Herbert Poetzl , Mikael Pettersson , Kernel Mailing List Subject: Re: Intel vs AMD x86-64 Message-ID: <20040225015251.GA5654@dingdong.cryptoapps.com> References: <7F740D512C7C1046AB53446D37200173EA2684@scsmsx402.sc.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7F740D512C7C1046AB53446D37200173EA2684@scsmsx402.sc.intel.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 24, 2004 at 03:15:18PM -0800, Nakajima, Jun wrote: > Near branch with 66H prefix: > As documented in PRM the behavior is implementation specific and > should avoid using 66H prefix on near branches. Presumably this isn't a problem with current gcc's right?