Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • asm asm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • asmasm
  • asmasm
  • Issues
  • #305716
Closed
Open
Issue created Jul 13, 2006 by kbr@kbr

Bug in floating point constant handling in constant pool writing

If a class containing the floating-point constant -0.0 is read in and
written out using ASM's ClassReader / ClassWriter pair, the -0.0
constants will be incorrectly translated to 0.0. The reason for this
is the equality comparison for single- and double-precision
floating-point Items; these should be performing bitwise equality
comparisons rather than using the floating-point equality comparisons
defined by the language. A patch for the Item class is attached. This
fix has been tested fairly extensively and solves this problem
apparently without introducing any new ones.
Assignee
Assign to
Time tracking