From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2537 invoked by alias); 28 Dec 2009 19:04:51 -0000 Received: (qmail 2429 invoked by uid 22791); 28 Dec 2009 19:04:50 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,DNS_FROM_RFC_BOGUSMX X-Spam-Check-By: sourceware.org Received: from sebabeach.org (HELO sebabeach.org) (64.165.110.50) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Dec 2009 19:04:47 +0000 Received: from sspiff.sspiff.org (seba.sebabeach.org [10.8.159.10]) by sebabeach.org (Postfix) with ESMTP id 175636E3D4; Mon, 28 Dec 2009 11:04:46 -0800 (PST) Message-ID: <4B39014D.4000203@sebabeach.org> Date: Mon, 28 Dec 2009 19:04:00 -0000 From: Doug Evans User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Dmitry Eremin-Solenikov CC: cgen@sourceware.org Subject: Re: cgen -> opcodes problem References: <20091227081006.GA23270@doriath.ww600.siemens.net> In-Reply-To: <20091227081006.GA23270@doriath.ww600.siemens.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00051.txt.bz2 Dmitry Eremin-Solenikov wrote: > Hello all, > > I'm back to my m68hc08 binutils port done via cgen. > Recently I've again stumbled upon a problem with instructions, > whose base? length != ISA base length. > > E.g. in the attached stripped test case, the 'ttt' instruction either > (should be assembled as 0x9E 0xF1) is misencoded as 0xsmth 0x00. > Is this my fault? Or is this the expected behaviour and I should define > f-seccode in some other way? > > Could you please help me? > > Hi. cgen currently doesn't handle instructions with opcode bits beyond the base insn size very well. I have a sandbox with this fixed, but it'll be awhile (month or more?) before it all gets checked in. In the meantime, setting base-insn-bitsize to 16 may work. [It *should* work, but there may be attributes of your port I haven't taken into account.]