From: James E Wilson <wilson@specifix.com>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: named address spaces (update)
Date: Thu, 07 Jul 2005 02:59:00 -0000 [thread overview]
Message-ID: <1120705060.11505.147.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <20050703143104.GA18820@ahab.auto.tuwien.ac.at>
On Sun, 2005-07-03 at 07:31, Martin Koegler wrote:
> * need to rewrite recursivly each element of type (which my contain structures,
> unions, ...) if a address space is set
> In http://gcc.gnu.org/ml/gcc/2005-04/msg01438.html, this was rated as bad idea.
It is possible I was wrong. Conceptually, this doesn't seem much
different than existing type qualifiers const/volatile, for which case
we must already have a solution. Maybe similar treatment will work for
named address spaces?
Otherwise, these answers all seem very reasonable.
One more thing occurred to me. An official patch will also require
documentation. We will need user documentation to explain the new
source code constructs and their behaviour. And we will need internals
documentation to explain the new macros, etc.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
next prev parent reply other threads:[~2005-07-07 2:59 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
2005-07-02 1:49 ` James E Wilson
2005-07-03 14:31 ` Martin Koegler
2005-07-07 2:59 ` James E Wilson [this message]
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=1120705060.11505.147.camel@aretha.corp.specifix.com \
--to=wilson@specifix.com \
--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).