From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 32E6E3858433; Tue, 20 Aug 2024 21:41:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 32E6E3858433 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1724190071; bh=NFNV4JNWq/7zx4KtKYwk24hqn39cAoZlT3/i+Hg9Y2c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jmlsH2Kfzk2jN3BkqMiyC0m2BJzGm6ajnTIov2JUHSQfRo+qoyPZJwAL6gTM3D1Z5 lAx8Aw9t3hEM/XsW2lVG1uNDO4yk1yHSXg0lwyBYIXRzK+SgtgGtYCqvJUcgQFQFig 3Ww7sBXxXAMKhlGeQP7HEF073GMLy9LJJnQHbE9Q= From: "gjl at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/116433] [AVR] cannot place template class static member variables in EEPROM Date: Tue, 20 Aug 2024 21:41:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gjl at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D116433 --- Comment #3 from Georg-Johann Lay --- (In reply to Andrew Pinski from comment #1) > The real fix is to have named address spaces support extended to C++. See > PR43745. That's a different issue. 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. When you want EEPROM support, you can just wrap routines from AVR-LibC. But that's not possible with PR43745 because there= is no way you can specify that VTABLEs be located in flash *and* to use the appropriate access instructions. It isn't possible in GCC either because j= ust putting VTALBEs in progmem won't fd the trick of using the right accessor instructions.=