← 返回首页
Simplified travis and added some new options by Zialus · Pull Request #809 · boostorg/compute · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted
Cancel Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search
Appearance settings
Resetting focus

Simplified travis and added some new options#809

Open
Zialus wants to merge 7 commits into
boostorg:developfrom
Zialus:travis-ci
Open

Simplified travis and added some new options#809
Zialus wants to merge 7 commits into
boostorg:developfrom
Zialus:travis-ci

Conversation

Copy link
Copy Markdown
Contributor

Zialus commented Jan 2, 2019 •
edited
Loading

Things left to do:

  • figure out why windows doesn't see any OpenCL platform/device
  • cache boost installation on windows
  • cache boost installation on osx/gcc combo

Copy link
Copy Markdown

coveralls commented Jan 2, 2019

Coverage remained the same at 84.02% when pulling eecaba1 on Zialus:travis-ci into 2135633 on boostorg:develop.

Copy link
Copy Markdown
Contributor Author

Zialus commented Jan 2, 2019 •
edited
Loading

@jszuppe could you help out with the caching of boost on windows?

I'm not sure what to do about the OpenCL part though. It's working fine on appveyor. https://ci.appveyor.com/project/Zialus/compute/builds/21322560

Copy link
Copy Markdown
Contributor

jszuppe commented Jan 2, 2019

@jszuppe could you help out with the caching boost on windows?

Sure, but first we need to make it detect an OpenCL device. For that you can use clinfo, no need to build Boost.Compute.

I'm not sure what to do about the OpenCL part though. It's working fine on appveyor.

Potential problems: MinGW-W64, intel 16.1.1 drivers (lack of support for used CPU). CMake can locate OpenCL.lib file installed using NuGet, I guess that's only ICD. The problem may be in locating .dll file provided by Intel with OpenCL implementation.

Copy link
Copy Markdown
Contributor Author

Zialus commented Jan 3, 2019

Result of running wmic cpu list full

AddressWidth=64 Architecture=9 Availability=3 Caption=Intel64 Family 6 Model 63 Stepping 0 ConfigManagerErrorCode= ConfigManagerUserConfig= CpuStatus=1 CreationClassName=Win32_Processor CurrentClockSpeed=2300 CurrentVoltage= DataWidth=64 Description=Intel64 Family 6 Model 63 Stepping 0 DeviceID=CPU0 ErrorCleared= ErrorDescription= ExtClock= Family=1 InstallDate= L2CacheSize= L2CacheSpeed= LastErrorCode= Level=6 LoadPercentage=9 Manufacturer=GenuineIntel MaxClockSpeed=2300 Name=Intel(R) Xeon(R) CPU @ 2.30GHz OtherFamilyDescription= PNPDeviceID= PowerManagementCapabilities= PowerManagementSupported=FALSE ProcessorId=1F8BFBFF000306F0 ProcessorType=3 Revision=16128 Role=CPU SocketDesignation=CPU 1 Status=OK StatusInfo=3 Stepping= SystemCreationClassName=Win32_ComputerSystem SystemName=PACKER-5BEC3ACC UniqueId= UpgradeMethod=1 Version= VoltageCaps=0

Copy link
Copy Markdown
Contributor Author

Zialus commented Jan 31, 2019

hey @jszuppe did you end up figuring something out about this?

I guess I could open a thread on travis community forum if you want me to.

Copy link
Copy Markdown
Contributor Author

Zialus commented Aug 15, 2019

Any updates on this?

I got no answers from the travis community - https://travis-ci.community/t/im-trying-to-use-opencl-but-clinfo-reports-0-platforms/2611

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

Footer

© 2026 GitHub, Inc.