Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 526
    • Issues 526
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1081

Closed
Open
Created Jun 10, 2019 by Michał Kępień@michalOwner

Statistics are broken in x86 Windows builds

Using atomic_int_fast64_t variables with atomic functions on x86 does not cause Visual Studio to report build errors, but such operations yield useless results. Since the isc_stat_t type is unconditionally typedef'd to atomic_int_fast64_t, any code performing atomic operations on isc_stat_t variables is broken in x86 Windows builds.

This was introduced in BIND 9.13.3, by commit e9e55cbd, which is part of !657 (merged). Every x86 Windows build produced since then has broken statistics.

Assignee
Assign to
Time tracking