From: Doug Evans <dje@transmeta.com>
To: Michael Meissner <cgen-mail@the-meissners.org>
Cc: cgen@sources.redhat.com
Subject: Re: Use of DI mode on 32-bit hosts
Date: Mon, 02 Jun 2003 22:10:00 -0000 [thread overview]
Message-ID: <16091.52049.933245.847188@casey.transmeta.com> (raw)
In-Reply-To: <20030602213329.GA8650@tiktok.the-meissners.org>
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 ....
next prev parent reply other threads:[~2003-06-02 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 17:32 Michael Meissner
2003-06-02 17:45 ` Doug Evans
2003-06-02 19:22 ` Michael Meissner
2003-06-02 20:44 ` Doug Evans
2003-06-02 20:50 ` Frank Ch. Eigler
2003-06-02 21:26 ` Doug Evans
2003-06-02 21:32 ` Frank Ch. Eigler
2003-06-02 22:04 ` Doug Evans
2003-06-03 15:19 ` Frank Ch. Eigler
2003-06-02 21:33 ` Michael Meissner
2003-06-02 22:10 ` Doug Evans [this message]
2003-06-02 22:16 ` Doug Evans
2003-06-04 20:27 ` Doug Evans
2003-06-05 11:51 ` Michael Meissner
2003-06-05 13:34 ` Ben Elliston
2003-06-05 15:41 ` Doug Evans
2003-06-05 16:04 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16091.52049.933245.847188@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen-mail@the-meissners.org \
--cc=cgen@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).