[go: up one dir, main page]

Skip to content
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

[blaze] Add lapack and openmp features #36786

Merged
merged 1 commit into from
Feb 22, 2024
Merged

Conversation

jbuonagurio
Copy link
Contributor
@jbuonagurio jbuonagurio commented Feb 16, 2024

Hi, this PR adds two feature flags to Blaze to allow for a minimal 'core' installation:

  1. lapack: LAPACK/BLAS is currently a default dependency, but its only required for certain matrix operations and BLAZE_BLAS_MODE which is off by default. See CMakeLists.txt#L65-L75.
  2. openmp: The absence of this flag actually disables SMP support entirely, so it might be better to just use smp instead. Thoughts? I used openmp for consistency with the existing port which explicitly sets the threading library via BLAZE_SMP_THREADS=OpenMP. In any case, Blaze defaults to OpenMP and removes BLAZE_SMP_THREADS from cache when BLAZE_SHARED_MEMORY_PARALLELIZATION is turned off. See CMakeLists.txt#L297-L304.

Both of these are still set as default features to ensure compatibility, though I think the default LAPACK REQUIRED as a reminder to package maintainers might be a bit excessive! If you're using LAPACK, you probably aren't relying on Blaze to import it for you. That's probably more of a discussion for upstream in any case.

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

@jbuonagurio
Copy link
Contributor Author

@microsoft-github-policy-service agree

@Cheney-W Cheney-W added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Feb 18, 2024
@Cheney-W
Copy link
Contributor

Please click the Ready for review button once you have finished this PR.

@jbuonagurio jbuonagurio marked this pull request as ready for review February 19, 2024 17:33
@Cheney-W Cheney-W added the info:reviewed Pull Request changes follow basic guidelines label Feb 20, 2024
@vicroms vicroms merged commit cf7d32c into microsoft:master Feb 22, 2024
17 checks passed
TomKatom pushed a commit to TomKatom/vcpkg that referenced this pull request Feb 23, 2024
Hi, this PR adds two feature flags to Blaze to allow for a minimal
'core' installation:

1. `lapack`: LAPACK/BLAS is currently a default dependency, but its only
required for certain matrix operations and `BLAZE_BLAS_MODE` which is
off by default. See
[CMakeLists.txt#L65-L75](https://bitbucket.org/blaze-lib/blaze/src/3156507a4b7a6a9cd413ef87df0a0aa2b1c697d9/CMakeLists.txt#lines-65:75).
2. `openmp`: The absence of this flag actually disables SMP support
entirely, so it might be better to just use `smp` instead. Thoughts? I
used `openmp` for consistency with the existing port which explicitly
sets the threading library via `BLAZE_SMP_THREADS=OpenMP`. In any case,
Blaze defaults to OpenMP and removes `BLAZE_SMP_THREADS` from cache when
`BLAZE_SHARED_MEMORY_PARALLELIZATION` is turned off. See
[CMakeLists.txt#L297-L304](https://bitbucket.org/blaze-lib/blaze/src/3156507a4b7a6a9cd413ef87df0a0aa2b1c697d9/CMakeLists.txt#lines-297:304).

Both of these are still set as default features to ensure compatibility,
though I think the default LAPACK REQUIRED as a reminder to package
maintainers might be a bit excessive! If you're using LAPACK, you
probably aren't relying on Blaze to import it for you. That's probably
more of a discussion for upstream in any case.

- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] ~~SHA512s are updated for each updated download.~~
- [ ] ~~The "supports" clause reflects platforms that may be fixed by
this new version.~~
- [ ] ~~Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~~
- [ ] ~~Any patches that are no longer applied are deleted from the
port's directory.~~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
Osyotr pushed a commit to Osyotr/vcpkg that referenced this pull request Feb 26, 2024
Hi, this PR adds two feature flags to Blaze to allow for a minimal
'core' installation:

1. `lapack`: LAPACK/BLAS is currently a default dependency, but its only
required for certain matrix operations and `BLAZE_BLAS_MODE` which is
off by default. See
[CMakeLists.txt#L65-L75](https://bitbucket.org/blaze-lib/blaze/src/3156507a4b7a6a9cd413ef87df0a0aa2b1c697d9/CMakeLists.txt#lines-65:75).
2. `openmp`: The absence of this flag actually disables SMP support
entirely, so it might be better to just use `smp` instead. Thoughts? I
used `openmp` for consistency with the existing port which explicitly
sets the threading library via `BLAZE_SMP_THREADS=OpenMP`. In any case,
Blaze defaults to OpenMP and removes `BLAZE_SMP_THREADS` from cache when
`BLAZE_SHARED_MEMORY_PARALLELIZATION` is turned off. See
[CMakeLists.txt#L297-L304](https://bitbucket.org/blaze-lib/blaze/src/3156507a4b7a6a9cd413ef87df0a0aa2b1c697d9/CMakeLists.txt#lines-297:304).

Both of these are still set as default features to ensure compatibility,
though I think the default LAPACK REQUIRED as a reminder to package
maintainers might be a bit excessive! If you're using LAPACK, you
probably aren't relying on Blaze to import it for you. That's probably
more of a discussion for upstream in any case.

- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] ~~SHA512s are updated for each updated download.~~
- [ ] ~~The "supports" clause reflects platforms that may be fixed by
this new version.~~
- [ ] ~~Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~~
- [ ] ~~Any patches that are no longer applied are deleted from the
port's directory.~~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants