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
  • #1998
Closed
Open
Issue created Dec 16, 2013 by J. Markiewicz@jmarkiewicz

Opus 1.1: 64 bit windows compilation generates conversion warnings

Using the 2010 projects to compile opus 1.1 and generate the following warnings compiling x64 Release.

opus_compare.c ....\src\opus_compare.c(78): warning C4244: '=' : conversion from 'int' to 'float', possible loss of data ....\src\opus_compare.c(233): warning C4244: '=' : conversion from 'double' to 'float', possible loss of data ....\src\opus_compare.c(349): warning C4244: '=' : conversion from 'double' to 'float', possible loss of data ....\src\opus_compare.c(367): warning C4244: '=' : conversion from 'double' to 'float', possible loss of data opus_decoder.c opus_encoder.c ....\src\opus_encoder.c(588): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(589): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(608): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(615): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(620): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(623): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(625): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) ....\src\opus_encoder.c(714): warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) repacketizer.c ....\src\repacketizer.c(222): warning C4244: '=' : conversion from '__int64' to 'int', possible loss of data

Maybe they are harmless, but they look scary especially when dealing we're talking about a codec. I didn't see a open issue filed on this so I thought I'd let you know.

Assignee
Assign to
Time tracking