-
Notifications
You must be signed in to change notification settings - Fork 273
Allow extra entry points loads to be specified [TG-4620] #2829
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
Conversation
Could you clarify how this compares to https://github.com/diffblue/cbmc/blob/develop/jbmc/src/java_bytecode/java_bytecode_language.cpp#L119 ? |
@smowton Gladly - the linked line is a list of functions to determine extra entry points. This list is currently ( This PR allows that same list to be additionally populated by classes implementing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks-- please write a bit of that (when to use the command-line arg, when to override the hook) as docs for the hook method, then lgtm.
@smowton docs updated - could you check they cover what you meant? |
4040cc0
to
26024f8
Compare
26024f8
to
b47f63e
Compare
Lazy methods can be extened to load additional methods as entry points. This allows this to be meaningfully used by subclasses of java_bytecode_language
Note use is_reference since java_generic_typet inherits from reference_typet so this stronger requirement more closely matches the class hierarchy.
b47f63e
to
232da1d
Compare
Belatedly confirmed this looks good! |
The extra entry points is to provide ways of extending the lazy methods entry points.
This also introduces an incidentally used
can_cast_type
forjava_generic_typet
TG bump (using this): diffblue/test-gen#2197