Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Opus Opus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 30
    • Issues 30
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.OrgXiph.Org
  • OpusOpus
  • Issues
  • #2048
Closed
Open
Issue created Sep 11, 2014 by Dave Michael@dmichael

Compiling without optimization produces a warning

I work on Chromium, and in my debug build, I always get this warning: src/src/opus_decoder.c:37:10: warning: You appear to be compiling without optimization, if so opus will be very slow. [-W#pragma-messages]

pragma message "You appear to be compiling without optimization, if so opus will be very slow."

     ^

I personally want my build output to be clean, and I'm perfectly aware when doing a debug build that it's debug and might be slow. So I would prefer if this warning was not there.

If it's not acceptable to simply remove this warning, it seems like it ought to be possible to turn this off with a precompile define so that embedders like Chromium can turn it off. We have a large code base and noise in our build output can be very annoying.

I'm willing to do the patch if there's an acceptable solution to this.

Assignee
Assign to
Time tracking