public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen-mail@the-meissners.org, cgen@sources.redhat.com
Subject: Re: Use of DI mode on 32-bit hosts
Date: Tue, 03 Jun 2003 15:19:00 -0000	[thread overview]
Message-ID: <20030603151925.GA7286@redhat.com> (raw)
In-Reply-To: <16091.51685.885875.214781@casey.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]

Hi -


On Mon, Jun 02, 2003 at 03:04:21PM -0700, Doug Evans wrote:
>  > I guess I don't see the abstraction and simplicity this
>  > indirection is to provide.  Do you have an example?
> 
> - I'd rather have one version of "add" for sparc 32/64

I would rather use macros that expand to SI or DI as appropriate
for the two different targets, or perhaps use DI only (and rely
on implicit truncation for 32-bit hardware registers).

> - I'd rather write 'IAI in the .scm sources when refering to 'pc
>   than doing something else

Likewise -- the PC register is likewise an inherently target-sized
quantity.

This whole argument sounds like going backward from the SI-vs-USI
issue from a few weeks ago.  It encodes in the type some notion of
purpose, or even a deliberate lack of specificity, instead of
leaving these solely in the operators.


>  > In what circumstances do you consider it reasonable for cgen
>  > model files to deal with host data types/sizes?
> 
> [...]
> Sometimes the code will need a mode but imposing a specific
> width muddies the waters.  If one wanted to write some rtl
> that looped over something, picking one of QI/HI/SI/DI
> may be less appealing than "just give me a big enough int". [...]

Not to me...  Given the low level nature of modelling semantics
in rtl, I don't consider it natural to pick "a big enough" int.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-03 15:19 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 [this message]
2003-06-02 21:33       ` Michael Meissner
2003-06-02 22:10         ` Doug Evans
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=20030603151925.GA7286@redhat.com \
    --to=fche@redhat.com \
    --cc=cgen-mail@the-meissners.org \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.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).