-
Notifications
You must be signed in to change notification settings - Fork 62
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
Misleading error message for unimplemented instructions #46
Comments
Hi, I see your point, However, I have no idea of how to get better error messages here. This probably means quite a lot of work and many tasks on herd7 are urgent. Hence this issue is not a high priority one, |
Ok, that’s fair enough. Perhaps we can meet this issue around and either
try to fix later or document somewhere that an error message like this can
simply mean that some construct is not known.
…On Wed, 9 Sep 2020 at 14.26, Luc Maranget ***@***.***> wrote:
Hi, I see your point,
However, I have no idea of how to get better error messages here. This
probably means quite a lot of work and many tasks on herd7 are urgent.
Hence this issue is not a high priority one,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#46 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIE24DZM2DKDIPDHG5VJ4LSE5YAVANCNFSM4QL7HD5Q>
.
|
one thought is that we could implement the parsing for instructions like this (I have implemented stlxp on my branch), and then add a 'not implemented' pattern in AArch64Sem: somewhere around? Line 640 in 82816da
of course it's up to us to add all the instruction variants, but this might work? |
hi Luke, if you've got an idea, please prepare a PR and we'll review then. |
same problem on |
Consider the following example used with the aarch64.cat model:
herd7 will complain because the STLXP instruction is not implemented, but the error message given is:
File "unknown-instr.litmus", line 7, characters 7-9: unexpected 'W0' (in prog) (User error)
If possible, it would improve usability in this scenario if the tool could report "Unrecognized statement 'STLXP'" or something like that instead.
The text was updated successfully, but these errors were encountered: