8000 Implement execution of swine-z3 on SMT2 files by SeRin-Yang · Pull Request #65 · moves-rwth/caesar · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Implement execution of swine-z3 on SMT2 files #65

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

Open
wants to merge 22 commits into
base: main
Choose a base branch
from

Conversation

SeRin-Yang
Copy link

No description provided.

Copy link
Collaborator
@Philipp15b Philipp15b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I've left a bunch of comments.

fn execute_swine(dir: &Path, file_path: &Path) {
let swine = "swine-z3";

let find_output = Command::new("find")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand wh 8000 y you'd be using find here? It should be sufficient to just do the call to swine directly.

.output().unwrap();

if cmd_output.status.success() {
println!("{}", String::from_utf8_lossy(&cmd_output.stdout));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The next step would be to parse the output of SWINE and return a SatResult.

println!("{}", String::from_utf8_lossy(&cmd_output.stdout));
break;
} else {
eprintln!("Failed to execute swine({}) command with status: {}", line, cmd_output.status);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, return a Result and return an error in this case.

}
}
} else {
eprintln!("Find command execution failed");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

}
}

fn remove_lines_for_swine(input: &str) -> String {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a doc comment saying which lines this removes.

@@ -94,6 +160,21 @@ impl<'ctx> Prover<'ctx> {
if self.min_level_with_provables.is_none() {
return ProveResult::Proof;
}

let mut smtlib = self.get_smtlib();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a next step, add an solver_type attribute of a new enum type SolverType with variants Z3 and SWINE, and then choose here whether to invoke either Z3 or SWINE.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can do this like we did it for SliceVerifyMethod and the SliceOptions::slice_verify_via option in main.rs.

}

#[derive(Debug)]
pub enum SolverType {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's introduce another SolverType here: SMTLIB(Command), which takes a Command object and uses it as a backend, just like we currently do for SWINE. Except that for SMTLIB, we don't remove the exp declaration.

Ok((SatResult::Unsat, "".to_string()))
} else if first_line.trim().to_lowercase() == "sat" {
let _last_line = lines_buffer.pop_back().ok_or(ProverCommandError::ParseError)?;
if _last_line.contains("SHA") {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks strange and at least requires a comment why that's here.

} else {
Err(ProverCommandError::ParseError)
}
} else {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should only return Unknown if the SAT solver result is actually unknown. If there's a different result than we expected, we must throw an error.

let mut input_buffer: VecDeque<char> = input.chars().collect();
let mut cnt = 0;

while let Some(c) = input_buffer.pop_front() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comment that you collect the full string for a (possibly multi-line) SMTLIB command by looking for the corresponding closed parenthesis, while counting nested parenthesis.

@@ -152,36 +243,76 @@ impl<'ctx> Prover<'ctx> {
self.add_assumption(&value.not());
self.min_level_with_provables.get_or_insert(self.level);
}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Be sure to have your editor automatically remove trailing spaces. cargo fmt --all should remove these as well, I think.

}
}
SolverType::Z3 => {
let res = match &self.last_result {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of this logic needs to happen for the SWINE calls as well! This includes returning cached results, checking with assumptions (where did the assumptions go when using SWINE??) and caching results afterwards.

ProveResult::Proof => {}
Ok(ProveResult::Unknown(reason)) => panic!("solver returned unknown ({})", reason),
Ok(ProveResult::Proof) => {},
Err(_) => {}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is the error here silently ignored?

@@ -15,6 +15,7 @@ thiserror = "1.0"
im-rc = "15"
enum-map = "2.7.3"
itertools = "0.14.0"
smtlib-lowlevel = "0.3.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we using this still?

@Philipp15b
Copy link
Collaborator
Philipp15b commented May 16, 2025

W.r.t. the "the Err-variant returned from this function is very large" clippy error, I've fixed those on the main branch just now (f8776cb). The other CI errors seem to come from this PR.

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.

2 participants
0