From tomorrow (wednesday 1st april) for three weeks I'll be away from
home.
I expect to be able to get online occasionally, but intermittently.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Test results for GNUstep as of Tue Mar 31 06:34:14 EDT 2009
If a particular system failed compilation, the logs for that system will
be placed at ftp://ftp.gnustep.org/pub/testfarm
If you would like to be a part of this automated testfarm, see
On 30 Mar 2009, at 16:37, David Chisnall wrote:
The remaining issue is that clang (and llvm-gcc, for that matter)
does not support the __builtin_apply() family of intrinsics. These
are quite unreliable on GCC, and it seems that they are not used
when FFCall or FFI is supported, but are
On 31 Mar 2009, at 17:13, Richard Frith-Macdonald wrote:
On 30 Mar 2009, at 16:37, David Chisnall wrote:
NSInvocation.m provides default implementations in terms of
__builtin_apply() and friends that are not used when libffi or
ffcall is provided. Is it possible to move these into a
Compiling file NSDistributedNotificationCenter.m ...
NSDistributedNotificationCenter.m: In function
‘-[NSDistributedNotificationCenter
addObserver:selector:name:object:suspensionBehavior:]’:
NSDistributedNotificationCenter.m:343: warning: cast from pointer to
integer of different size
Am Dienstag, den 31.03.2009, 22:13 +0100 schrieb David Chisnall:
On 31 Mar 2009, at 20:00, David Ayers wrote:
I'm mostly concerned about keeping support for deprecated API which
was
1) part of either the OpenStep specification.
2) part of OPENSTEP 4.2 (widely distributed cross
On 1 Apr 2009, at 00:28, David Ayers wrote:
Am Dienstag, den 31.03.2009, 22:13 +0100 schrieb David Chisnall:
On 31 Mar 2009, at 20:00, David Ayers wrote:
If we can implement the argframe approach (ie. -forward::) via
libffi
then we could also resolve some long standing libobjc issues. Yet
From the mailing list when I asked this last, and from comparing the
list of supported platforms for the two. Again, can you name one
platform supported by ffcall and GNUstep, but not libffi? Does anyone
want to jump in and say 'My platform doesn't support libffi! Please
don't
On 1 Apr 2009, at 00:56, Pete French wrote:
My platform (FreeBSD/amd64) supports ffcall but not libffi (or
this was the case last time I compiled GNUstep about a month ago)
so please don't drop support :-)
The FreeBSD port for libffi is not marked as broken on amd64. I'd be
very surprised
On Tue, Mar 31, 2009 at 4:56 PM, Pete French p...@twisted.org.uk wrote:
All the rest of the email, however, I agree with - the lack of
ObjC maintenance on GCC worries me greatly. I depend on this
stuff for my living, and for my business to make sales. Having
somewhere else to jump to would
Well if your business depends on it, you might want to hire someone
someone to do the development.
Well, that would be me. But I kind of have a lot of other stuff to
do. I'll reprhrase it as I dont want to take this on myself.
Apple has moved away from GCC so you can no longer depend on them.
Would it be possible for you to check whether GNUstep works with
libffi? On FreeBSD/i386, it defaults to using ffcall, but works
better with libffi (i.e. doesn't randomly corrupt the stack when you
pass NSInvocations between threads). You probably need to explicitly
specify
On Tue, Mar 31, 2009 at 5:51 PM, Pete French p...@twisted.org.uk wrote:
Well if your business depends on it, you might want to hire someone
someone to do the development.
Well, that would be me. But I kind of have a lot of other stuff to
do. I'll reprhrase it as I dont want to take this on
I should have said moving away but really they are so close to have
moved away, it can be considered moved.
So what have they moved to out of interest, or can't you tell us ?
Is this just for Obj-C or the whole operating system ?
-pete.
___
14 matches
Mail list logo
