Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Merge requests
  • !468

Merged
Created Jan 16, 2021 by kraus@krausDeveloper

Don't use GLIBCXX_ASSERTIONS in production

  • Overview 14
  • Commits 4
  • Changes 2

Closes #627 (closed)

I assumed that this flag GLIBCXX_ASSERTIONS has no effect when the build type is Release. However I did some timing measurements and observed an increase of ~6 percent when using. This is fine for development builds but not for production.

Edited Jan 16, 2021 by kraus
Assignee
Assign to
Reviewer
Request review from
OPAL 2021.1
Milestone
OPAL 2021.1 (Past due)
Assign milestone
Time tracking
Source branch: 627-add-wp-d_glibcxx_assertions-to-the-build-flags-3