I assume by dirty, you mean flip the bit in the card table corresponding to the memory location in which a potential cross-generational pointer is being stored. Also when you refer to base I assume you mean the start of the object containing the memory location. In this case you don't need to do anything, GC will scan the whole object to update the potential cross generational pointers even if the objects spans multiple cards some of which are not flipped. The brick table is used to found the start of the first object outside the card that has been flipped.
I am not sure why you would want to flip cards at compile time, but you could call FJit_pHlpAssign_Ref(ptr, current_value). Vladimir This posting is provided "AS IS" with no warranties, and confers no rights. -----Original Message----- From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL PROTECTED] On Behalf Of Archana Sent: Monday, January 12, 2004 9:26 PM To: [EMAIL PROTECTED] Subject: [DOTNET-ROTOR] the write barrier Hi, The function FJit_pHlpAssign_Ref(ptr, val) appears to dirty the slot of the object getting updated. if one wants to dirty the base of the object instead, is it possible to accomplish this at compile time. if so, can you please guide me to the place where changes need to be done. Regards, Archana =================================== This list is hosted by DevelopMentor(r) http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
