public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mojo at world3 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63760] Support __func__ in PROGMEM
Date: Thu, 06 Nov 2014 11:36:00 -0000	[thread overview]
Message-ID: <bug-63760-4-7Vtv6otmTW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63760-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760

--- Comment #2 from mojo at world3 dot net ---
On platforms with this kind of architecture the default is to place everything
in RAM, unless you specifically state otherwise.

With Harvard style architectures different instructions are used to access RAM
and program memory. GCC doesn't handle that natively, so you need to add things
like PROGMEM or __flash to tell it where to store and how to access the data.


       reply	other threads:[~2014-11-06 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63760-4@http.gcc.gnu.org/bugzilla/>
2014-11-06 11:36 ` mojo at world3 dot net [this message]
2014-11-14 22:21 ` gjl at gcc dot gnu.org
2014-11-14 23:02 ` mojo at world3 dot net

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=bug-63760-4-7Vtv6otmTW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).