This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 187
Create release 1.6.0. #191
Merged
Merged
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,9 +11,37 @@ It pulls in the latest version of upstream libc++ and marks the beginning of | |
|
||
!--> | ||
|
||
## libcu++ 1.6.0 (CUDA Toolkit 11.5) | ||
|
||
libcu++ 1.6.0 is a major release. It adds two new functions to the `cuda::std::barrier` API and | ||
uses `<nv/target>` as the primary dispatch mechanism for `cuda::std::atomic`. This is an ABI breaking release. | ||
|
||
Supported ABI Versions: 4 (default), 3, and 2. | ||
|
||
Included in: CUDA Toolkit 11.5. | ||
|
||
### New Features | ||
|
||
- #111: Adds two APIs to `cuda::std::barrier` for waiting on the parity of the barrier. | ||
- Thanks to Olivier Giroux for this contribution. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Technically speaking we don't need to call out Olivier as he's a core contributor, but it's fine. Always good to thank people. |
||
|
||
### Issues fixed | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed should be capitalized. |
||
|
||
- #179: Refactors the atomic layer to allow for layering the host device/host abstractions. | ||
- #189: Changed pragmas for silencing chrono long double warnings. | ||
- #186: Allows `<nv/target>` to be used under NVRTC. | ||
- #177: Allows `<nv/target>` to build when compiled under C and C++98. | ||
- Thanks to David Olsen for this contribution. | ||
- #172: Introduces ABI version 4. | ||
- Forces `cuda::std::complex` alignment for enhanced performance. | ||
- Sets the internal representation of `cuda::std::chrono` literals to `double`. | ||
- #165: For tests on some older distributions keep using Python 3, but downgrade lit. | ||
- #164: Fixes testing issues related to Python 2/3 switch for lit. | ||
- Thanks to Royil Damer for this contribution. | ||
|
||
## libcu++ 1.5.0 (CUDA Toolkit 11.4) | ||
|
||
libcu++ 1.5.0 is a major release. It adds `<nv/target>`, | ||
libcu++ 1.5.0 is a major release. It adds `<nv/target>`, | ||
the library support header for the new `if target` | ||
target specialization mechanism. | ||
|
||
|
This file contains 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go look up the changelog entry for the last new ABI, and make sure we are using the same wording. I think the summary for the last ABI change explained that the new one was now the default, and that the old one was still supported.