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

Do second round API detect for optimizer if needed #1557

Merged
merged 3 commits into from
May 21, 2024
Merged

Do second round API detect for optimizer if needed #1557

merged 3 commits into from
May 21, 2024

Conversation

JerryAMD
Copy link
Collaborator

Problem
For some cases, 1000 blocks is not enough for API detection.

Solution
If the first round detection with 1000 blocks doesn't return any detection result, we will do a second round API detection with no-block-limit parameter. The detection will be done with no block limit, till one of targeted API calls is found. A message will show in the console if the second round is needed.

Result
It looks for most cases, 1000 blocks should be enough for the API detection. The second round detection should always give us the result and it will be performed only the first round detection (short) doesn't provide any result.

Problem
For some cases, 1000 blocks is not enough for API detection.

Solution
If the first round detection with 1000 blocks doesn't return any detection result, we will do a second round API detection with no-block-limit parameter. The detection will be done with no block limit, till one of targeted API calls is found. A message will show in the console if the second round is needed.

Result
It looks for most cases, 1000 blocks should be enough for the API detection. The second round detection should always give us the result and it will be performed only the first round detection (short) doesn't provide any result.
@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 186720.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 4191 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 4191 passed.

@davidd-lunarg
Copy link
Contributor

Looks good, but it needs clang format before it can be merged.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 189406.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 4227 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 4227 passed.

@davidd-lunarg davidd-lunarg merged commit 46c524d into LunarG:dev May 21, 2024
8 checks passed
@JerryAMD JerryAMD deleted the dev-jerry-apidetect branch May 22, 2024 17:44
locke-lunarg pushed a commit to locke-lunarg/gfxreconstruct that referenced this pull request Jun 10, 2024
Problem
For some cases, 1000 blocks is not enough for API detection.

Solution
If the first round detection with 1000 blocks doesn't return any detection result, we will do a second round API detection with no-block-limit parameter. The detection will be done with no block limit, till one of targeted API calls is found. A message will show in the console if the second round is needed.

Result
It looks for most cases, 1000 blocks should be enough for the API detection. The second round detection should always give us the result and it will be performed only the first round detection (short) doesn't provide any result.
locke-lunarg pushed a commit to locke-lunarg/gfxreconstruct that referenced this pull request Jun 10, 2024
Problem
For some cases, 1000 blocks is not enough for API detection.

Solution
If the first round detection with 1000 blocks doesn't return any detection result, we will do a second round API detection with no-block-limit parameter. The detection will be done with no block limit, till one of targeted API calls is found. A message will show in the console if the second round is needed.

Result
It looks for most cases, 1000 blocks should be enough for the API detection. The second round detection should always give us the result and it will be performed only the first round detection (short) doesn't provide any result.
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