Skip to content

Navigation Menu

Appearance settings

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

diffblue / cbmc Public

Notifications You must be signed in to change notification settings
Fork 274
Star 923

Code
Issues 428
Pull requests 144
Actions
Projects 4
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Use CPROVER_PREFIX macro instead of hardcoded __CPROVER_ string#3171

Merged

tautschnig merged 3 commits intodiffblue:developdiffblue/cbmc:developfrom

tautschnig:use_cprover_prefixtautschnig/cbmc:use_cprover_prefixCopy head branch name to clipboard

Oct 29, 2018

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Oct 29, 2018

Use CPROVER_PREFIX macro instead of hardcoded __CPROVER_ string
tautschnig
committed
Linter and clang-format ignores, and whitespace cleanup
tautschnig
committed
Check for uses of __CPROVER_ in the linter
tautschnig
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.