From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15403 invoked by alias); 2 Jun 2003 22:10:44 -0000 Mailing-List: contact cgen-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sources.redhat.com Received: (qmail 15384 invoked from network); 2 Jun 2003 22:10:43 -0000 Received: from unknown (HELO neon-gw.transmeta.com) (63.209.4.196) by sources.redhat.com with SMTP; 2 Jun 2003 22:10:43 -0000 Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id PAA05075; Mon, 2 Jun 2003 15:10:38 -0700 Received: from mailhost.transmeta.com(10.1.1.15) by neon-gw.transmeta.com via smap (V2.1) id xma004978; Mon, 2 Jun 03 15:10:21 -0700 Received: from casey.transmeta.com (casey.transmeta.com [10.10.25.22]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id h52MAQB24051; Mon, 2 Jun 2003 15:10:26 -0700 (PDT) Received: (from dje@localhost) by casey.transmeta.com (8.9.3/8.7.3) id PAA17197; Mon, 2 Jun 2003 15:10:25 -0700 From: Doug Evans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16091.52049.933245.847188@casey.transmeta.com> Date: Mon, 02 Jun 2003 22:10:00 -0000 To: Michael Meissner Cc: cgen@sources.redhat.com Subject: Re: Use of DI mode on 32-bit hosts In-Reply-To: <20030602213329.GA8650@tiktok.the-meissners.org> References: <20030602173232.GA5871@tiktok.the-meissners.org> <16091.36137.249864.565465@casey.transmeta.com> <20030602192217.GA7082@tiktok.the-meissners.org> <16091.46855.343504.902253@casey.transmeta.com> <20030602213329.GA8650@tiktok.the-meissners.org> X-SW-Source: 2003-q2/txt/msg00073.txt.bz2 Michael Meissner writes: > Something like c99's inttypes.h (which has types for give me an integer that is > exactly 32-bit longs, and give me an integer that is at least 32-bits long, but > could be larger depending on the local conditions). Something along those lines, though I try to approach these things by only adding as warranted. > > 4) This doesn't address INT/UINT. Ideally it would remain 32 bits > > (i.e. a portable int). > > Or maybe they should be slated to be removed. Except that I missed the part about them also being used to represent arbitrary width types. > I dunno what we should do about the SIMD vector types (ie, V2QI, V8DI, etc.). > Most machines these days do have MMX/VIS/SSE/SSE2/etc. type instructions. The > machine I'm targetting has a rather complete set of these instructions. Well, a minimalist approach could be taken and say they aren't needed (and neither is SF/DF/etc. btw), the argument being the same as for the (intended) absence of USI in .cpu files: it's the operation that specified the type, not the data. OTOH, they can simplify things downstream ....