This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe
- From: "rfm at gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 17 Mar 2011 20:21:27 +0000
- Subject: [Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe
- Auto-submitted: auto-generated
- References: <bug-38307-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38307
rfm at gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #17020|0 |1
is obsolete| |
--- Comment #8 from rfm at gnu dot org 2011-03-17 20:21:13 UTC ---
Created attachment 23702
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23702
David's patch with a few more fixes and updated for current svn trunk
Made it safe to modify class methods during +initialize (eg as done by class
clusters adding behaviors in gnustep).
Made it safe for superclass +initialize to use the subclass.
Simplified message lookup so that get_imp and objc_msg_lookup share common
code, reducing the chance of a mistake in this tricky class initialisation
process.