From: "E. Weddington" <ericw@evcohs.com>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: "Björn Haase" <bjoern.m.haase@web.de>, gcc@gcc.gnu.org
Subject: Re: named address spaces (update)
Date: Wed, 29 Jun 2005 15:37:00 -0000 [thread overview]
Message-ID: <42C2BFCE.9010304@evcohs.com> (raw)
In-Reply-To: <20050629084740.GA8315@ahab.auto.tuwien.ac.at>
Martin Koegler wrote:
>I continued to work on the support for named address spaces in GCC. I
>managed to move much of the managing code for the namespace attribute
>into the create funtions of tree nodes, so in most cases, only the
>language frontends need to assign and check the named address spaces.
>
>I moved to creation of the namespace list to the gen-modes program
>(all examples are taken out of my m68hc05 GCC port
>http://www.auto.tuwien.ac.at/~mkoegler/index.php/gcc ). A named
>address space is allocated with NAMESPACE(name) in the mode definition
>file of the port, eg:
>
>NAMESPACE(EEPROM);
>NAMESPACE(LORAM);
>
>(I know, that the NAMESPACE is not the correct naming, but named
>address space is a bit too long. Any suggestions?)
>
>
Because it's a space of addresses (as opposed to a space of names), how
about this?:
ADDRESSSPACE (EEPROM);
ADDRESSSPACE (LORAM);
Eric
next prev parent reply other threads:[~2005-06-29 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 8:48 Martin Koegler
2005-06-29 12:18 ` DJ Delorie
2005-06-29 15:38 ` E. Weddington
2005-06-29 13:15 ` Daniel Jacobowitz
2005-06-29 15:37 ` E. Weddington [this message]
2005-07-02 1:49 ` James E Wilson
2005-07-03 14:31 ` Martin Koegler
2005-07-07 2:59 ` James E Wilson
2005-07-08 1:55 Paul Schlie
2005-07-10 14:41 ` Martin Koegler
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=42C2BFCE.9010304@evcohs.com \
--to=ericw@evcohs.com \
--cc=bjoern.m.haase@web.de \
--cc=gcc@gcc.gnu.org \
--cc=mkoegler@auto.tuwien.ac.at \
/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).