From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2575 invoked by alias); 1 Oct 2009 16:34:21 -0000 Received: (qmail 2565 invoked by uid 22791); 1 Oct 2009 16:34:20 -0000 X-SWARE-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp1.mail.completel.net (HELO smtp1.mail.completel.net) (213.245.2.32) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Oct 2009 16:34:16 +0000 Received: from [192.168.1.100] (unknown [213.244.2.35]) by smtp1.mail.completel.net (Postfix) with ESMTP id C33F920007; Thu, 1 Oct 2009 18:34:13 +0200 (CEST) Message-ID: <4AC4DA04.7080503@joguin.com> Date: Thu, 01 Oct 2009 16:34:00 -0000 From: Jean-Marc Saffroy User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Doug Evans CC: cgen@sourceware.org Subject: Re: problem with 64-bit arch References: <4AC4BF97.8040302@joguin.com> <4AC4D17D.30308@sebabeach.org> In-Reply-To: <4AC4D17D.30308@sebabeach.org> 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/msg00003.txt.bz2 Doug Evans wrote: > We were just discussing instruction word bitsizes of 64, and it's not > clear what to do. > I don't mind going down the path of having 64 bit instructions expressed > as a single 64 bit integer (*1), but can you confirm your architecture > has 64-bit instructions? From the given sample, it seems like it has 32 > bit instructions and 64-bit words (like sparc64). You guessed right: my target arch has 32 bit instructions (which I expressed with base-insn-bitsize == 32), and uses 64-bit words for data and addresses (expressed with word-bitsize == 64). > Clearly the missing type in the cast is a bug. That should be easy to > fix. As for the use of long to record a 64-bit value, that should also > be (relatively) easy to fix. > I'll dig deeper tonight. Good to hear, thanks! I found the cast could be fixed by changing the "(dfm 'DI..." line in mode.scm, but have no idea about the possible side effects, and didn't find a cure for the use of long anyway. Cheers, JM