Searched full:description (Results 1 – 6 of 6) sorted by relevance
3 description: |
41 | Function Pointer | Description |
565 --description "$(PROOF_UID): removing static"580 --description "$(PROOF_UID): building project binary"592 --description "$(PROOF_UID): building proof binary"604 --description "$(PROOF_UID): removing function bodies from project sources"615 --description "$(PROOF_UID): linking project to proof"627 --description "$(PROOF_UID): restricting function pointers in project sources"639 --description "$(PROOF_UID): setting static variables to nondet"651 --description "$(PROOF_UID): dropping unused functions"663 --description "$(PROOF_UID): slicing global initializations"677 --description "$(PROOF_UID): replacing function calls with function contracts"[all …]
22 DESCRIPTION = "Configure and run all CBMC proofs in parallel" variable92 description=DESCRIPTION, epilog=EPILOG,
7 description: 'Commit ID to tag and create a release for'10 description: 'Release Version Number (Eg, v1.0.0)'13 description: 'Is this a re-release of existing tag/release? (Default: false)'
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description45 # quick idea about the purpose of the project. Keep the description short.104 # description of a member or function before the detailed description112 # This tag implements a quasi-intelligent brief description abbreviator that is114 # as the leading text of the brief description, will be stripped from the text116 # text. Otherwise, the brief description is used as-is. If left blank, the135 # description.185 # description. If set to NO, the Javadoc-style will behave just like regular Qt-187 # description.)203 # line (until the first dot) of a Qt-style comment as the brief description. If[all …]
