[swift-corelibs-dev] libdispatch prep for integration to the rest of swift-corelibs

Philippe Hausler phausler at apple.com
Wed Jan 13 14:40:25 CST 2016


Almost all of the Foundation overlay stuff we have had to integrate directly into Foundation itself (which has made some of the build process a bit funky). The one to watch out for is @_silgen_name since that cannot be used outside of the stdlib.

> On Jan 13, 2016, at 12:35 PM, Chris Bailey <BAILEYC at uk.ibm.com> wrote:
> 
> I believe another task for the list of libdispatch integration items is the implementation of the Dispatch overlay for Linux. I've been taking a stab at that based on changes made (and then reverted) by Slava in November - hopefully I'll have something worth looking at for it tomorrow.
> 
> 
> 
> 
> From:        Pierre Habouzit via swift-corelibs-dev <swift-corelibs-dev at swift.org> 
> To:        Philippe Hausler <phausler at apple.com> 
> Cc:        Swift Core Libs <swift-corelibs-dev at swift.org> 
> Date:        13/01/2016 20:04 
> Subject:        Re: [swift-corelibs-dev] libdispatch prep for integration to the rest of swift-corelibs 
> Sent by:        swift-corelibs-dev-bounces at swift.org 
> 
> 
> 
> it needs pthread wq changes that are still in review (the pull request is tagged as such). 
> 
> -Pierre 
> 
> On Jan 13, 2016, at 11:11 AM, Philippe Hausler via swift-corelibs-dev <swift-corelibs-dev at swift.org <mailto:swift-corelibs-dev at swift.org>> wrote: 
> 
> Splitting this off to it’s own thread since this is not per-se networking related 
> 
> On Jan 13, 2016, at 11:07 AM, David P Grove <groved at us.ibm.com <mailto:groved at us.ibm.com>> wrote: 
> phausler at apple.com <mailto:phausler at apple.com> wrote on 01/13/2016 01:43:17 PM:
> > 
> > Getting GCD up and rolling is definitely a bottleneck for a few 
> > things (not just NSURLSession). 
> 
> Thanks Philippe!  I was looking for things to do :)
> 
> > 
> > There are a few things that we need as checkpoints:
> > A set of build instructions tailored for the swift project
> > GCD needs to be able to build on Ubuntu 14 as well as Ubuntu 15
> 
> I can take a look at Ubuntu 14.  I know that one of the issues was the old version of libpthread_workqueue (under discussion for other reasons; we need fixes that aren't in the Ubuntu 15 version).  I'll see if there is anything else standing in the way for Ubuntu 14.
> 
> 
> I am getting a build failure on 14: 
> 
> /bin/bash ../libtool  --tag=CC   --mode=compile clang -DHAVE_CONFIG_H -I. -I../config  -I.. -I.. -I../private -I../os -DDISPATCH_USE_DTRACE=0 -Wall -fvisibility=hidden -momit-leaf-frame-pointer  -I/usr/include/kqueue   -isystem /usr/include/bsd -DLIBBSD_OVERLAY   -fblocks -g -O2 -c -o queue.lo queue.c 
> libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../config -I.. -I.. -I../private -I../os -DDISPATCH_USE_DTRACE=0 -Wall -fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue -isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -g -O2 -c queue.c  -fPIC -DPIC -o .libs/queue.o 
> queue.c:216:22: error: use of undeclared identifier 'WORKQ_BG_PRIOQUEUE' 
>                 .dgq_wq_priority = WORKQ_BG_PRIOQUEUE, 
>                                    ^ 
> queue.c:227:22: error: use of undeclared identifier 'WORKQ_BG_PRIOQUEUE' 
>                 .dgq_wq_priority = WORKQ_BG_PRIOQUEUE, 
>                                    ^ 
> queue.c:928:18: error: invalid application of 'sizeof' to an incomplete type 'struct dispatch_root_queue_context_s []' 
> 
> > We need to move Availability.h and friends down underneath both GCD 
> > and Foundation since they both use them
> > We need to move the blocks runtime out of Foundation and underneath 
> > or inside of GCD.
> > The master build script in swift/utils/build-script needs to be able
> > to build GCD
> > The master build script in swift/utils/build-script to ensure GCD 
> > and all required components are built before Foundation and the 
> > appropriate linker paths are passed to Foundation (see how XCTest is handled)
> > 
> 
> --dave
> 
> 
> 
> _______________________________________________
> swift-corelibs-dev mailing list
> swift-corelibs-dev at swift.org <mailto:swift-corelibs-dev at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev <https://lists.swift.org/mailman/listinfo/swift-corelibs-dev> 
> 
> _______________________________________________
> swift-corelibs-dev mailing list
> swift-corelibs-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev <https://lists.swift.org/mailman/listinfo/swift-corelibs-dev>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20160113/af64facc/attachment.html>


More information about the swift-corelibs-dev mailing list