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.

Sign up for GitHub

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

Jump to bottom

Support calling the constructors in llvm.global_ctors #357

Open
langston-barrett opened this issue Jan 22, 2019 · 2 comments
Open

Support calling the constructors in llvm.global_ctors #357

langston-barrett opened this issue Jan 22, 2019 · 2 comments
Labels
needs design Technical design work is needed for issue to progress subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm type: feature request Issues requesting a new feature or capability unsoundness Issues that can lead to unsoundness or false verification
Milestone
2025T1

Comments

@langston-barrett
Copy link
Contributor

langston-barrett commented Jan 22, 2019 •
edited
Loading

C++ code (e.g. anything in iostream) depends on the constructors in the llvm.global_ctors global variable being called before any functions are run. These might call arbitrary code (and so should probably not be run by default), but we should have an option to run them when the user asks.

See GaloisInc/crucible#145
@langston-barrett langston-barrett self-assigned this Jan 22, 2019
@atomb atomb added this to the 1.0 milestone Jun 4, 2019
@langston-barrett langston-barrett added the subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm label Jun 7, 2019
@langston-barrett
Copy link
Contributor Author

Related discussion: GaloisInc/crucible#286

@atomb atomb removed this from the 0.5 milestone Apr 3, 2020
@kquick kquick added the needs design Technical design work is needed for issue to progress label Jul 16, 2021
@brianhuffman
Copy link
Contributor

#916 deals with a related issue for JVM.

@sauclovian-g sauclovian-g added unsoundness Issues that can lead to unsoundness or false verification type: feature request Issues requesting a new feature or capability labels Oct 29, 2024
@sauclovian-g sauclovian-g added this to the 2025T1 milestone Oct 29, 2024
@sauclovian-g sauclovian-g mentioned this issue Oct 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs design Technical design work is needed for issue to progress subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm type: feature request Issues requesting a new feature or capability unsoundness Issues that can lead to unsoundness or false verification
Projects
None yet
Milestone
2025T1
Development

No branches or pull requests
5 participants
@atomb @brianhuffman @kquick @langston-barrett @sauclovian-g