From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33593 invoked by alias); 12 May 2015 14:49:38 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 33574 invoked by uid 89); 12 May 2015 14:49:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ob0-f172.google.com Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 12 May 2015 14:49:36 +0000 Received: by obcus9 with SMTP id us9so7344170obc.2 for ; Tue, 12 May 2015 07:49:34 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.225.65 with SMTP id y62mr11685764oig.78.1431442174427; Tue, 12 May 2015 07:49:34 -0700 (PDT) Received: by 10.76.54.14 with HTTP; Tue, 12 May 2015 07:49:34 -0700 (PDT) In-Reply-To: References: <20150511212331.GA1838@intel.com> <5551F4E70200007800079575@mail.emea.novell.com> <55520C440200007800079718@mail.emea.novell.com> <555216370200007800079773@mail.emea.novell.com> Date: Tue, 12 May 2015 14:49:00 -0000 Message-ID: Subject: Re: [committed, PATCH] Remove Disp16|Disp32 from 64-bit direct branches From: "H.J. Lu" To: Michael Matz Cc: Jan Beulich , Binutils Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00088.txt.bz2 On Tue, May 12, 2015 at 7:31 AM, Michael Matz wrote: > Hi, > > On Tue, 12 May 2015, H.J. Lu wrote: > >> > This is with 2.23, so your patch would cause a regression: >> >> 1. This happened before 20140923. > > Same with current 2.25-branch. > >> 2. Can you speculate what >> >> " jmpw 4" >> >> does? > > It should do a jump to $nextip+offset, of course, just like a 32bit > jump. The disassembly is correct, because with a zero offset, that's > indeed '4'. > I thought it did jump to "(nextip + offset) & 0xffff" on AMD. Can you verify if it is true? -- H.J.