Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 861
    • Issues 861
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 55
    • Merge requests 55
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and 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
  • GNOMEGNOME
  • GLib
  • Merge requests
  • !1558

Allow instance/class private size bigger than 64k

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Sebastian Dröge requested to merge sdroege/glib:allow-big-private-data into master Jun 30, 2020
  • Overview 17
  • Commits 1
  • Pipelines 1
  • Changes 1

There is no actual reason for it being limited to 64k. For the public instance/class structs the 64k limit exists because of the limitations of GTypeInfo but there is no such limitation here.

As in various places we sum up all the private struct sizes and still require the sum to be smaller than 64k, it can relatively easily happen that some type is hitting the limit. As this can also happen for example when adding a private field to some base class, which then breaks a subclass that happens to use just too much data now, this means adding private fields can cause ABI breakage.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: allow-big-private-data