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

Confusing variable names in error messages of the (S)CT checkers #810

Open
vbgl opened this issue May 28, 2024 · 0 comments
Open

Confusing variable names in error messages of the (S)CT checkers #810

vbgl opened this issue May 28, 2024 · 0 comments

Comments

@vbgl
Copy link
Member

vbgl commented May 28, 2024

Here is an example of an insecure program:

inline fn f(reg u64 y x) {
  if y == x {
  }
}

export fn noct(#secret reg u64 x) {
  f(x, 0);
}

When running the CT checker on it after the rmphi pass (e.g., using jazzct --after=rmphi notct.jazz), it produces the following message:

"notct.jazz", line 2 (5-6):
constant type checker: x has type secret it needs to be public

Of course, x here refers to the parameter y of function f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant