Differences between revisions 5 and 6
Revision 5 as of 2019-09-11 17:53:08
Size: 1917
Comment:
Revision 6 as of 2019-09-11 18:16:33
Size: 2232
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
  * ltrace/latrace/audit status
    * DJ to give some status update.
    * Merge latrace and ltrace?
    * Put it on gitlab, and call it part of the official glibc audit framework?
    * Have resurrected ltrace.
    * latrace is dead.
Line 10: Line 16:
    * Ask reviewers to give “Reviewed-by:” so we can thank them all.     * https://sourceware.org/glibc/wiki/Contribution%20checklist%20v2
    * Just a reminder to go read the checklist and see if it looks good.
Line 13: Line 20:
  * latrace/audit integration
    * Merge latrace and ltrace?
    * Put it on gitlab, and call it part of the official glibc audit framework?
  * Building independent parts of glibc
    * A libglibcmalloc.so - Independent malloc for testing experimental changes?
    * A libm.so & libmvec.so - Revisit discussion?
    * Does this matter if we are going to having just one library?
  * Update the glibc build infrastructure
    * Discuss getting accurate dependency information into the build system so we can do incremental build and test in as fast a time as possible.
    * Breaking up tests? Fast. Short. Fixed time.
Line 22: Line 33:
  * Building independent parts of glibc
    * A libglibcmalloc.so - Independent malloc for testing experimental changes?
    * A libm.so & libmvec.so - Revisit discussion?
    * Does this matter if we are going to having just one library?
  * Update the glibc build infrastructure
    * Discuss getting accurate dependency information into the build system so we can do incremental build and test in as fast a time as possible.
Line 36: Line 41:
    * Adding GLIBC_EXP symbol versions? How do you go from an experimental ABI to a stable one?

GNU Cauldron 2019 Agenda

On XXXX 2019 the GNU C Library community held a BoF at GNU Cauldron 2019.

  • Buildbot awareness and status.
    • How does one fix buildbot issues?
      • Who is responsible for each buildbot?
    • Who is responsible for fixing a regression?
  • ltrace/latrace/audit status
    • DJ to give some status update.
    • Merge latrace and ltrace?
    • Put it on gitlab, and call it part of the official glibc audit framework?
    • Have resurrected ltrace.
    • latrace is dead.
  • Contribution Checklist v2
  • GLIBC_PRIVATE mangling
    • Break applications using GLIBC_PRIVATE by mangling the symbol at every release or build?
  • Building independent parts of glibc
    • A libglibcmalloc.so - Independent malloc for testing experimental changes?
    • A libm.so & libmvec.so - Revisit discussion?

    • Does this matter if we are going to having just one library?
  • Update the glibc build infrastructure
    • Discuss getting accurate dependency information into the build system so we can do incremental build and test in as fast a time as possible.
    • Breaking up tests? Fast. Short. Fixed time.
  • Put glibc on gitlab?
    • Inconvenient to move.
    • Adds a PR workflow for those that like that.
    • Still supports email-based workflow.
    • Faster access to repository via Gitlab's servers (tested faster than sourceware).
    • Provides CI hooks for running build-many-glibcs for each PR.
  • How do we, as a core library, promote research into:
    • Extending the core APIs?
    • Change core behavior?
    • Add new tool interfaces?
    • Adding GLIBC_EXP symbol versions? How do you go from an experimental ABI to a stable one?

GNU Cauldron 2019 Notes

Notes to go here.

None: Cauldron2019 (last edited 2019-09-25 17:32:45 by CarlosODonell)