From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17679 invoked by alias); 6 May 2005 13:57:01 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 17665 invoked from network); 6 May 2005 13:56:58 -0000 Received: from unknown (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68) by sourceware.org with SMTP; 6 May 2005 13:56:58 -0000 Received: from mace ([192.168.1.25]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.211); Fri, 6 May 2005 14:56:57 +0100 From: "Dave Korn" To: "'Jan Beulich'" , Subject: RE: [PATCH] x86: suppress emission of zero displacements in memoryoperands Date: Fri, 06 May 2005 14:00:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 06 May 2005 13:56:57.0058 (UTC) FILETIME=[77783420:01C55243] X-SW-Source: 2005-05/txt/msg00256.txt.bz2 ----Original Message---- >From: Jan Beulich >Sent: 06 May 2005 13:04 > When explicitly specified, gas encoded a pointless zero displacement in > memory addressing forms. Since this is not normally desired and was most > likely just an oversight, this patch adds an adjustment to eliminate the > displacement in that case. I'm not sure if I've fully understood the intent of this patch, but I think you're saying that if someone writes mov %eax,0(%edi) the assembler will emit 4 0003 8907 mov %eax,(%edi) and not 2 0000 894700 mov %eax,0(%edi) yes? Nothing the user _explicitly_ specifies should ever be discarded IMO. What if someone wants to write self-modifying code that stores varying offsets into that field? cheers, DaveK -- Can't think of a witty .sigline today....