public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "digger1984 at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/116433] [AVR] cannot place template class static member variables in EEPROM
Date: Wed, 21 Aug 2024 07:57:53 +0000	[thread overview]
Message-ID: <bug-116433-4-7g6yrSqKJU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116433-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from C.F. <digger1984 at gmx dot com> ---
(In reply to Georg-Johann Lay from comment #3)
> EEPROM handling is too complicated, we don't want
> /that/ code in the compiler and support > 300 devices where each one might
> need different SFR handling.

Out of curiosity I'd like to know and understand why it is complicated. I'm not
questioning it is, I'd really like to understand why it is so. Explained in
laymans' terms, preferably. Also, are you talking about just AVR (which is
relevant to this bug and duplicates I suppose)? Or are you talking more in the
general sense?

> When you want EEPROM support, you can just wrap routines from AVR-LibC.

Well, that precisely *is* what I had wished I could avoid and make EEPROM
storage transparent, looking like accessing ordinary variables using a bit of
"C++ magic". I guess I'm back to the drawing board then...

      parent reply	other threads:[~2024-08-21  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 17:42 [Bug c++/116433] New: [AVR] cannot place template class static members " digger1984 at gmx dot com
2024-08-20 17:46 ` [Bug target/116433] [AVR] cannot place template class static member variables " pinskia at gcc dot gnu.org
2024-08-20 17:55 ` digger1984 at gmx dot com
2024-08-20 21:41 ` gjl at gcc dot gnu.org
2024-08-21  7:57 ` digger1984 at gmx dot com [this message]

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-116433-4-7g6yrSqKJU@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).