Skip to content

clarify config of pthread_workqueue vs. internal_workqueue #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 25, 2017

Conversation

dgrove-oss
Copy link
Contributor

As suggested in review of PR-206, DISPATCH_USE_INTERNAL_WORKQUEUES
should not enable HAVE_PTHREAD_WORKQUEUES. Instead, a new
DISPATCH_USE_WORKQUEUES is defined in queue.c to guard code that
should be enabled in either case.

As suggested in review of PR-206, DISPATCH_USE_INTERNAL_WORKQUEUES
should not enable HAVE_PTHREAD_WORKQUEUES.  Instead, a new
DISPATCH_USE_WORKQUEUES is defined in queue.c to guard code that
should be enabled in either case.
@dgrove-oss
Copy link
Contributor Author

@MadCoder, I guess this needs to be tested by Swift CI and then it can be merged?

@MadCoder
Copy link
Contributor

Yes. I'm not suer why I forgot to fire it

@swift-ci please test

@das das merged commit 5a3c02a into swiftlang:master May 25, 2017
@dgrove-oss dgrove-oss deleted the queue_config_cleanup branch May 25, 2017 13:03
das added a commit that referenced this pull request Jul 31, 2017
clarify config of pthread_workqueue vs. internal_workqueue

Signed-off-by: Daniel A. Steffen <dsteffen@apple.com>
@das das removed the darwin pending label Aug 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants