public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	<gdb-patches@sources.redhat.com>, <cgen@sources.redhat.com>
Subject: Re: [Sim] Patch to sim/common/cgen-ops.h
Date: Mon, 04 Dec 2000 10:53:00 -0000	[thread overview]
Message-ID: <14891.59391.397233.55439@casey.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012041725200.4024-100000@moshpit.cygnus.com>

Ben Elliston writes:
 >     > Why is CGEN follow the GCC convention of SI, UI, BI, ZI, NFI, rather
 >     > than the sim-common convention of signed8, unsigned64, ...
 > 
 >    'cus cgen rtl is based on gcc rtl and I like having the types be the
 >    same in the emitted code as in the rtl.
 > 
 > I think Andrew was asking why the rtl uses these names.  Using other names
 > for the modes would not preclude the use of an rtl, it just wouldn't look
 > like GCC's.  Is that a bad thing, given that it would allow the programmer
 > to be more explicit about data representation on the target side?

Andrew may have just been refering to the name choice used in the
generated code.  Either way, this is just a naming choice issue.
I like the current scheme.

  reply	other threads:[~2000-12-04 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200012040402.eB442Sk23037@scooby.cygnus.com>
2000-12-03 20:12 ` Andrew Cagney
2000-12-03 21:09   ` Doug Evans
2000-12-03 22:27     ` Ben Elliston
2000-12-04 10:53       ` Doug Evans [this message]
2000-12-04 14:31         ` Andrew Cagney
2000-12-04  4:55   ` Frank Ch. Eigler

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=14891.59391.397233.55439@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=ac131313@cygnus.com \
    --cc=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=gdb-patches@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).