[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #9382] mframe vs. gcc/libobjc selector types

From: David Ayers
Subject: [bugs #9382] mframe vs. gcc/libobjc selector types
Date: Fri, 18 Jun 2004 13:07:58 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608

This mail is an automated notification from the bugs tracker
 of the project: GNUstep.

[bugs #9382] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9382>
Project: GNUstep
Submitted by: David Ayers
On: Fri 06/18/2004 at 17:08

Category:  Base/Foundation
Severity:  5 - Average
Item Group:  Bug
Resolution:  None
Assigned to:  None
Status:  Open

Summary:  mframe vs. gcc/libobjc selector types

Original Submission:  We use the platform dependent mframe code to implement 
NSMethodSignature's method types while gcc/libobjc uses a platform independent 
encoding scheme (well in pre 3.4 version it wasn't fully platform independent 
as it marked where registers were used depending on the platform but the "ObjC 
improvements" merge broke that.)  Unfortunately we use these mframe signatures 
to register selectors for DO (see Testing/nsnotification).  Yet the mframe 
encoding "dialects" cannot be handled by libobjc which causes objc_error aborts 
on some platforms (e.g. linux/hppa but potentially others) when selectors are 
registered with those types.  I believe we need to reorganize NSMethodSignature 
to use the "gcc/libobjc" encoding dialect instead of the mframe dialects which 
should be resrced for DO processing.  I haven't looked into how this could be 
done yet.  Maybe someone a bit more familiar with this code may want to jump in 
and have a look at it.  Riccardo
Mottola can provide information (if I'm not available) and test.  Otherwise 
I'll drop it on my TODO list.

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]