From: Paolo Bonzini <bonzini@gnu.org>
To: gcc@gcc.gnu.org
Subject: Re: RFC embedded c proposal
Date: Thu, 29 Apr 2004 11:57:00 -0000 [thread overview]
Message-ID: <4090B771.4070906@gnu.org> (raw)
In-Reply-To: <4090B26B.4050002@solidas.com>
> b) Declare an __attribute__, e.g. __attribute__((progmem)), that will
> become a part of the type decleration:
>
> __attribute__((progmem)) char a, b, c; // Works today in GCC
>
> __attribute__((progmem)) int *p; // Does not work
>
>
> Which of these two methods would be best suited for gcc?
I think this one; then if you want you can use builtin_define in the
target's TARGET_CPU_CPP_BUILTINS #define, to define _Progmem to be
__attribute__ ((progmem)). This is how AltiVec works, at least.
Paolo
next prev parent reply other threads:[~2004-04-29 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 11:25 Svein E. Seldal
2004-04-29 11:57 ` Paolo Bonzini [this message]
2004-04-29 12:51 ` Giovanni Bajo
2004-04-29 16:19 ` Joseph S. Myers
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=4090B771.4070906@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
/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).