[all-commits] [llvm/llvm-project] 303f24: [libc] Make template_header optional for hdrgen (#...

[Roland McGrath via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 303f2415448ac79fa85abd22ad7108fbb9dab3d3
      https://github.com/llvm/llvm-project/commit/303f2415448ac79fa85abd22ad7108fbb9dab3d3
  Author: Roland McGrath <mcgrathr at google.com>
  Date:   2025-02-14 (Fri, 14 Feb 2025)

  Changed paths:
    R libc/include/ctype.h.def
    M libc/include/ctype.yaml
    M libc/utils/hdrgen/header.py
    M libc/utils/hdrgen/main.py
    M libc/utils/hdrgen/tests/expected_output/subdir/test.h
    R libc/utils/hdrgen/tests/input/subdir/test.h.def
    M libc/utils/hdrgen/tests/input/subdir/test.yaml
    M libc/utils/hdrgen/yaml_to_classes.py

  Log Message:
  -----------
  [libc] Make template_header optional for hdrgen (#127259)

This allows a YAML file to omit `template_header` and have no
`.h.def` file.  A default template is generated based purely on
the information in the YAML file.  This should handle most of the
cases.  For now, it's exercised (aside from the hdrgen tests)
only for one of the simplest cases: <ctype.h>.

This includes making the parser notice the "standards" YAML field
at the top (header) level, not just in "functions" lists.  The
standards listed for the header overall and for the individual
functions both feed into how a fully-generated header describes
itself in comments.  To go with this, files using the default
generated template must stick to a new uniform set of spellings
for the "standards" lists.  As more custom template files are
retired, the corresponding YAML files will need all their
standards lists normalized.  For now, ctype.yaml is updated
with correct attribution for the POSIX `_l` extensions.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications