Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M margo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sds
  • margo
  • Issues
  • #61

Closed
Open
Created Apr 29, 2020 by Matthieu Dorier@mdorierOwner

Add support for new Mercury functions

The following functions have been added to Mercury (or never had a margo version) and a margo_ version should be made available:

  • HG_Bulk_bind
  • HG_Bulk_get_addr
  • HG_Bulk_get_serialize_cached_ptr
  • HG_Bulk_get_serialize_cached_size
  • HG_Bulk_set_serialize_cached_ptr
  • HG_Bulk_bind_transfer
  • HG_Class_get_name
  • HG_Class_get_protocol
  • HG_Class_get_input_eager_size
  • HG_Class_get_output_eager_size
  • HG_Class_set_input_offset
  • HG_Class_set_output_offset
  • HG_Class_set_data
  • HG_Class_get_data
  • HG_Class_set_handle_create_callback
  • HG_Context_set_data
  • HG_Context_get_data
  • HG_Registered_proc_cb
  • HG_Addr_set_remove
  • HG_Addr_cmp
  • HG_Reset
  • HG_Ref_get
  • HG_Set_data
  • HG_Get_data
  • HG_Get_input_buf
  • HG_Get_output_buf
  • HG_Get_input_extra_buf
  • HG_Get_output_extra_buf
  • HG_Cancel

For some of these functions it's a matter of defining a macro. For some other, they have to work on a margo instance instead of an hg_class or an hg_context. And for some, we use them internally in margo and the wrapper should do something slightly different (i.e. HG_Class_set_input_offset should take into account the fact that we are setting an offset ourselves for the breadcrumb).

Assignee
Assign to
Time tracking