search for: apple_versioning

...gcc anyway) 3) "#pragma mark" isn't supported by FSF gcc, so "#if 0" it out. It should still show up in IDEs that support it 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. function pointers can't be cast to void * either. 5) Avoid a warning for apple_versioning.c that "ISO C does not allow empty files" Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to define and copy some blocks (and invoke them, obviously). Also tested on Mac OS X 10.6 and linking against -lBlocksRuntime ahead of -lSystem. -------------- next part ----...

...quot;#pragma mark" isn't supported by FSF gcc, so "#if 0" it out. It should > still show up in IDEs that support it > 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. > function pointers can't be cast to void * either. > 5) Avoid a warning for apple_versioning.c that "ISO C does not allow empty > files" > > Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to define > and copy some blocks (and invoke them, obviously). Also tested on Mac OS X > 10.6 and linking against -lBlocksRuntime ahead of -lSystem. > > &l...

...'t supported by FSF gcc, so "#if 0" it out. It >> should >> still show up in IDEs that support it >> 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. >> function pointers can't be cast to void * either. >> 5) Avoid a warning for apple_versioning.c that "ISO C does not >> allow empty >> files" >> >> Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to >> define >> and copy some blocks (and invoke them, obviously). Also tested on >> Mac OS X >> 10.6 and linking ag...

...y FSF gcc, so "#if 0" it out. It >>> should >>> still show up in IDEs that support it >>> 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. >>> function pointers can't be cast to void * either. >>> 5) Avoid a warning for apple_versioning.c that "ISO C does not allow >>> empty >>> files" >>> >>> Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to >>> define >>> and copy some blocks (and invoke them, obviously). Also tested on Mac OS >>> X >&g...

...It >>>> should >>>> still show up in IDEs that support it >>>> 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about >>>> %p. >>>> function pointers can't be cast to void * either. >>>> 5) Avoid a warning for apple_versioning.c that "ISO C does not >>>> allow >>>> empty >>>> files" >>>> >>>> Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to >>>> define >>>> and copy some blocks (and invoke them, obviously)....

...It >>>>> should >>>>> still show up in IDEs that support it >>>>> 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. >>>>> function pointers can't be cast to void * either. >>>>> 5) Avoid a warning for apple_versioning.c that "ISO C does not allow >>>>> empty >>>>> files" >>>>> >>>>> Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to >>>>> define >>>>> and copy some blocks (and invoke them, obvious...

...hread_key and with this modified libc++abi.dylib, all the symbols are found, things work correctly, and all the tests that should pass in the llvm "testit" suite do pass. I presume that the visibility of ___emutls_get_address in libclang_rt.osx.a is being controlled by some mechanism (apple_versioning.c ?). I notice that the library is built with -fvisibility=hidden 1) is my approach here generally reasonable? 2) is there a toggle to allow the ___emutls_get_address symbol in libclang_rt.10.4.a to be made visible to libc++abi.dylib ? Best, Ken

...>>> still show up in IDEs that support it >>>>>> 4) Fix some compiler warnings. GCC 4.3.3 seems super strict >>>>>> about %p. >>>>>> function pointers can't be cast to void * either. >>>>>> 5) Avoid a warning for apple_versioning.c that "ISO C does not >>>>>> allow >>>>>> empty >>>>>> files" >>>>>> >>>>>> Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and - >>>>>> fblocks to >>>>>>...