Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix bounds check for FAST Nonmax#3357

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
jlaxson wants to merge2 commits intoarrayfire:master
base:master
Choose a base branch
Loading
fromjlaxson:fix-cpu-fast-dims

Conversation

jlaxson
Copy link

@jlaxsonjlaxson commentedJan 24, 2023
edited
Loading

This bounds check was broken in two ways:

  1. It happened after memory access already occurred, meaning it didn't really protect anything
  2. It swapped x/y checks in the dimension order.

The result was fast (and orb) features would not be returned for the entire image if the input image wasn't square.

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • Functions added to unified API
  • Functions documented

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
3.9.0
Development

Successfully merging this pull request may close these issues.

2 participants
@jlaxson@syurkevi

[8]ページ先頭

©2009-2025 Movatter.jp