From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2724 invoked by alias); 20 Aug 2008 19:36:35 -0000 Received: (qmail 2715 invoked by uid 22791); 20 Aug 2008 19:36:34 -0000 X-Spam-Check-By: sourceware.org Received: from mexforward.lss.emc.com (HELO mexforward.lss.emc.com) (128.222.32.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 20 Aug 2008 19:35:54 +0000 Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id m7KJZnI8023468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Aug 2008 15:35:50 -0400 (EDT) Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by hop04-l1d11-si03.isus.emc.com (Tablus Interceptor) for ; Wed, 20 Aug 2008 15:02:18 -0400 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id m7KJZVEC005429 for ; Wed, 20 Aug 2008 15:35:35 -0400 (EDT) From: jon.busenkell@rsa.com Received: from CORPUSMX50C.corp.emc.com ([128.221.62.45]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Aug 2008 15:34:54 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: C++ objects with virtual tables in eeprom Date: Wed, 20 Aug 2008 20:24:00 -0000 Message-ID: <8051C0C0C5D53544833F107546C5323302DBC1A6@CORPUSMX50C.corp.emc.com> To: X-Tablus-Inspected: yes X-Tablus-Classifications: public X-Tablus-Action: allow Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-08/txt/msg00205.txt.bz2 Hello all: I am wondering if anyone has ever implemented a __attribute__ or #pragma statement for use with constructors to specify to the compiler that the object does not exist in ram; therefore it can not just do a "MOV.L ," with the register containing the virtual tables address. The compiler I am presently using (from the chip vendor) does not take into account that C++ objects that have virtual tables, might reside in the eeprom. I am asking them to add this feature, and they are asking me if there is a standard way of handling this. Any thoughts would be greatly appreciated. Thank you, Jon