Skip to content

Conversation

focusexplorer
Copy link

It seems that LBR_NFA_VSHUF has no effect and will cause compilation errors

hongyang7 and others added 2 commits March 6, 2023 16:30
Roll back fix for github issue intel#350

About Scratch Usage:
For compile time, scratch space is strongly recommended to be
allocated immediately after database generation.
For runtime, besides using scratch for corresponding database,
Hyperscan also allows user to use larger scratch space allocated
for another database.
When multiple concurrent threads need to use the same databases
and a new scratch space is required, cloning the largest one is
always safe. This is realized based on API hs_scratch_size() and
hs_clone_scratch().
Behaviors beyond above are discouraged and results are undefined.
@fatchanghao
Copy link
Contributor

will you give more detail about your issue, like the platform you're running, how you build, what's the error message?

@focusexplorer
Copy link
Author

focusexplorer commented Mar 9, 2023 via email

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