-
Notifications
You must be signed in to change notification settings - Fork 63
Issues: GaloisInc/saw-script
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
saw-core-what4
: Support SMT arrays with record/tuple elements
subsystem: saw-core
#1988
opened Nov 21, 2023 by
RyanGlScott
Don't concretize applications of uninterpreted functions in SAW's symbolic simulator
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: enhancement
Issues describing an improvement to an existing feature or capability
#1906
opened Aug 14, 2023 by
RyanGlScott
Typeclass system to make saw-core more readable
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: feature request
Issues requesting a new feature or capability
#1845
opened Mar 21, 2023 by
m-yac
SAW's simulator doesn't short-circuit evaluation like Cryptol does
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
#1820
opened Feb 9, 2023 by
RyanGlScott
Incorrect simulation when indexing into array using out-of-bounds bitvector
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
#1807
opened Jan 26, 2023 by
RyanGlScott
Remove scFinVal from SharedTerm library
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
#1611
opened Mar 15, 2022 by
brianhuffman
Simplify Issues related to the saw-core representation or the saw-core subsystem
tech debt
Issues that document or involve technical debt
NameInfo
type
subsystem: saw-core
#1581
opened Feb 15, 2022 by
brianhuffman
Bad line breaks and indentation in pretty-printed saw-core terms
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
#1580
opened Feb 15, 2022 by
brianhuffman
Attach names to arbitrary saw-core subterms
subsystem: cryptol-saw-core
Issues related to Cryptol -> saw-core translation with cryptol-saw-core
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
#1569
opened Feb 8, 2022 by
brianhuffman
SharedTerm and Recognizer differ on what a tuple is
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
#1383
opened Jul 20, 2021 by
eddywestbrook
Term ordering for permutative rewriting
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Internal consistency of saw-core typechecking
needs design
Technical design work is needed for issue to progress
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
tech debt
Issues that document or involve technical debt
type: enhancement
Issues describing an improvement to an existing feature or capability
ruleOfProp is a bit clunky
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
unsoundness
Issues that can lead to unsoundness or false verification
sawcore imports don't work correctly
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Separate saw-core modules can't define constants with the same base name
needs test
Issues for which we should add a regression test
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
tech debt
Issues that document or involve technical debt
topics: saw-core names
Issues related to URI-based saw-core names
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Add support for serializing / deserializing SAW core modules to/from disk
needs design
Technical design work is needed for issue to progress
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: feature request
Issues requesting a new feature or capability
What4 backend with appended boolean list literals causes blowup in term size
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
print_goal
doesn't show the types of quantified variables
easy
Feature request: subterm evaluation
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: feature request
Issues requesting a new feature or capability
Unfolding rejects the names of fields
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: enhancement
Issues describing an improvement to an existing feature or capability
Uninterpreted higher-order functions
needs test
Issues for which we should add a regression test
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: enhancement
Issues describing an improvement to an existing feature or capability
Records in saw-script have lost their field names, making reading difficult
subsystem: cryptol-saw-core
Issues related to Cryptol -> saw-core translation with cryptol-saw-core
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
scCryptolType: unsupported type sort 0
needs test
Issues for which we should add a regression test
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: bug
Issues reporting bugs or unexpected/unwanted behavior
More evaluation for Technical design work is needed for issue to progress
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
tech debt
Issues that document or involve technical debt
type: enhancement
Issues describing an improvement to an existing feature or capability
crucible_term
and friends
needs design
Prime field inverses
missing cryptol features
Issues about features in Cryptol that don't work in SAW
subsystem: cryptol-saw-core
Issues related to Cryptol -> saw-core translation with cryptol-saw-core
subsystem: saw-core
Issues related to the saw-core representation or the saw-core subsystem
type: feature request
Issues requesting a new feature or capability
Previous Next
ProTip!
Follow long discussions with comments:>50.