-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add can_read to memories #267
Conversation
FYI this is coming from Adrian's email |
I think the problem is with this line: Line 95 in 6e7419e
Should be |
@alexreinking The line is fine, it's trying to say that whoever inherits this class should specify if the memory is readable or not, which I think is fair. |
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.
No reason to skip this test.
tests/test_neon.py
Outdated
|
||
import numpy as np | ||
|
||
|
||
@pytest.mark.isa("neon") |
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.
This test doesn't actually run anything on NEON, it just needs to get as far as generating C. Therefore it should never be skipped and you can check that read_neon.c_code_str()
throws the expected MemGenError
.
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.
That makes sense!
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.
Looks good when green
I have no idea why we didn't discover this until now...