Hi Gregory, We are indeed not very good at calling destructors, and I have started fixing this a few times only to hit issues with events that are scheduled (and complain when deleted). We could either set a flag and force the deletion, or be very well-behaved and force things to drain/quiesce. In any case there is some work needed.
Andreas On 14/04/2015 08:02, "VAUMOURIN Grégory" <[email protected]> wrote: >Hello everyone, > >I have a naive question. I'm trying to simulate some memory hierarchies >with Ruby and it seems to me that the destructors of the Cache Memory >objects created for the simulation are not called. Which object is in >charge of destroying the cache memories ? Because the Cache Controller >have the pointer to the cache memory object but it never calls the >destructors . >(I'm using the MESI protocol) > >-- >Gregory Vaumourin > > >_______________________________________________ >gem5-dev mailing list >[email protected] >http://m5sim.org/mailman/listinfo/gem5-dev -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782 _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
