[Bug objc/94637] @selector() broken for selectors containing repeated colons

2020-04-17 Thread rfm at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94637 --- Comment #1 from rfm at gnu dot org --- *** Bug 94638 has been marked as a duplicate of this bug. ***

[Bug objc/94638] @selector() broken for selectors containing repeated colons

2020-04-17 Thread rfm at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94638 rfm at gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution

[Bug objc/94637] New: @selector() broken for selectors containing repeated colons

2020-04-17 Thread rfm at gnu dot org
Priority: P3 Component: objc Assignee: unassigned at gcc dot gnu.org Reporter: rfm at gnu dot org Target Milestone: --- The compiler fails to compile legal Objective-C programs which use the @selector() syntax to send message to objects, if those messages have multiple

[Bug objc/94638] New: @selector() broken for selectors containing repeated colons

2020-04-17 Thread rfm at gnu dot org
Priority: P3 Component: objc Assignee: unassigned at gcc dot gnu.org Reporter: rfm at gnu dot org Target Milestone: --- The compiler fails to compile legal Objective-C programs which use the @selector() syntax to send message to objects, if those messages have multiple

[Bug libobjc/80393] New: class_replaceMethod() can modify the wrong class

2017-04-11 Thread rfm at gnu dot org
Component: libobjc Assignee: unassigned at gcc dot gnu.org Reporter: rfm at gnu dot org Target Milestone: --- The current implementation in libobjc is IMP class_replaceMethod (Class class_, SEL selector, IMP implementation, const char *method_types) { struct

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2011-04-02 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38307 rfm at gnu dot org changed: What|Removed |Added Attachment #23702|0 |1 is obsolete

[Bug libobjc/48177] incorrect registration of typed selectors

2011-03-21 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48177 --- Comment #4 from rfm at gnu dot org 2011-03-21 10:08:31 UTC --- The bug did cause proxies to fail ... but I implemented a workaround for that in base, so it's not critical for gnustep once the new base is released (and older versions of base

[Bug libobjc/48177] New: incorrect registration of typed selectors

2011-03-18 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48177 Summary: incorrect registration of typed selectors Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libobjc AssignedTo:

[Bug libobjc/48177] incorrect registration of typed selectors

2011-03-18 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48177 --- Comment #2 from rfm at gnu dot org 2011-03-18 14:58:10 UTC --- The problem showed up with argframe information in base ... which presumably means that something in base is getting that wrong :-( I wonder, could we have a runtime function

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2011-03-17 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38307 --- Comment #6 from rfm at gnu dot org 2011-03-17 06:20:42 UTC --- I spent some hours looking at your code and I like it ... it's certainly clearer than mine. I found three problems which i've fixed on my system: 1. failure to check CLS_ISRESOLV

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2011-03-17 Thread rfm at gnu dot org
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

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2011-03-16 Thread rfm at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38307 --- Comment #4 from rfm at gnu dot org 2011-03-16 12:43:39 UTC --- I just searched this old bug report up, and found that I'd missed seeing (or forgotten about) the latest response :-( I've been running with my patch for a couple of years without

[Bug libffi/41908] closures fail for some structure arguments containing floats

2009-11-12 Thread rfm at gnu dot org
--- Comment #4 from rfm at gnu dot org 2009-11-12 11:48 --- I'm a bit disappointed at the lack of activity on this bug report. I've been looking at the libffi code myself (though I'm certainly no expert at this low-level stuff) and have come up with two issues: 1. If I edit libffi

[Bug libffi/41908] New: closures fail for some structure arguments containing floats

2009-11-02 Thread rfm at gnu dot org
floats Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libffi AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rfm at gnu dot org GCC build triplet

[Bug libffi/41908] closures fail for some structure arguments containing floats

2009-11-02 Thread rfm at gnu dot org
--- Comment #1 from rfm at gnu dot org 2009-11-02 15:58 --- Created an attachment (id=18950) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18950action=view) test code for bug 419087 This is test code adapted from the libffi testsuite ... it could be added as a new regression test

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2009-01-01 Thread rfm at gnu dot org
--- Comment #2 from rfm at gnu dot org 2009-01-01 15:02 --- Created an attachment (id=17020) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17020action=view) Patch for sendmsg.c to fix this bug I've been using this patch for a while ... it modifies sendmsg.c to prevent the bug

[Bug libobjc/27466] RFE: Support for libobjc equivalent of std::set_unexpected

2009-01-01 Thread rfm at gnu dot org
--- Comment #5 from rfm at gnu dot org 2009-01-01 15:08 --- I just checked up on this again ... The problem was initially reported two and a half years ago. I supplied a (very very simple) patch to fix it a month ago. Could someone please apply the patch so it gets into the next

[Bug libobjc/27466] RFE: Support for libobjc equivalent of std::set_unexpected

2008-12-17 Thread rfm at gnu dot org
--- Comment #4 from rfm at gnu dot org 2008-12-17 09:36 --- Is anyone monitoring/progressing this bug? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27466

[Bug libobjc/27466] RFE: Support for libobjc equivalent of std::set_unexpected

2008-12-08 Thread rfm at gnu dot org
--- Comment #3 from rfm at gnu dot org 2008-12-08 08:29 --- Any news on when this can be done? The path is tiny/trivial, so even though it might be judged low priority I'd have hoped it could be fitted in quickly. -- rfm at gnu dot org changed: What|Removed

[Bug libobjc/38307] Calling of the +initialize method is not completely thread-safe

2008-12-08 Thread rfm at gnu dot org
--- Comment #1 from rfm at gnu dot org 2008-12-08 08:39 --- It turns out that solving this bug, even though it's conceptually simple, is quite a lot of work. I have new code to fix it, but it took me a whole day to develop and involves extensive additions and alterations to sendmsg.c

[Bug c/38338] New: Compile abort when compiling code which used to work

2008-11-30 Thread rfm at gnu dot org
used to work Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rfm at gnu dot org GCC build triplet: i686-pc-linux-gnu

[Bug libobjc/27466] RFE: Support for libobjc equivalent of std::set_unexpected

2008-11-28 Thread rfm at gnu dot org
--- Comment #2 from rfm at gnu dot org 2008-11-28 15:56 --- Created an attachment (id=16787) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16787action=view) An implementation of objc_set_unexpected function We really need this function to use native objective-c in GNUstep

[Bug libobjc/38307] New: Calling of the +initialize method is not completely thread-safe

2008-11-28 Thread rfm at gnu dot org
Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libobjc AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rfm at gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38307