-
Notifications
You must be signed in to change notification settings - Fork 708
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
Incorrect cmake version #4
Comments
Thanks for the bug report, fixed in b776138. We decided to not add a workaround, as it is hard to do in a cross-platform manner, and 2.8.11 should be available on most recent distros. |
Closed
fatchanghao
pushed a commit
that referenced
this issue
Apr 21, 2022
Throw std::bad_alloc instead of returning nullptr from ue2::AlignedAllocator. Allocators for STL containers are expected never to return with an invalid pointer, and instead must throw on failure. Violating this expectation can lead to invalid pointer dereferences. Co-authored-by: johanngan <johanngan.us@gmail.com>
fatchanghao
pushed a commit
that referenced
this issue
Apr 21, 2022
Throw std::bad_alloc instead of returning nullptr from ue2::AlignedAllocator. Allocators for STL containers are expected never to return with an invalid pointer, and instead must throw on failure. Violating this expectation can lead to invalid pointer dereferences. Co-authored-by: johanngan <johanngan.us@gmail.com> fixes github issue #317 (PR #320)
fatchanghao
pushed a commit
that referenced
this issue
Feb 15, 2023
Throw std::bad_alloc instead of returning nullptr from ue2::AlignedAllocator. Allocators for STL containers are expected never to return with an invalid pointer, and instead must throw on failure. Violating this expectation can lead to invalid pointer dereferences. Co-authored-by: johanngan <johanngan.us@gmail.com>
cosmicexplorer
pushed a commit
to cosmicexplorer/hyperscan
that referenced
this issue
Dec 30, 2023
Throw std::bad_alloc instead of returning nullptr from ue2::AlignedAllocator. Allocators for STL containers are expected never to return with an invalid pointer, and instead must throw on failure. Violating this expectation can lead to invalid pointer dereferences. Co-authored-by: johanngan <johanngan.us@gmail.com> fixes github issue intel#317 (PR intel#320)
GerHobbelt
pushed a commit
to GerHobbelt/hyperscan
that referenced
this issue
May 10, 2024
improve the performance on aarch64 platform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The required version for cmake should be 2.8.11. The string(TIMESTAMP ...) directive was released in 2.8.11 but is not available in previous versions.
It could be nice to provide a workaround as well.
The text was updated successfully, but these errors were encountered: