[all-commits] [llvm/llvm-project] c99602: [libc] Provide an implementation of the 'stdint.h'...

Joseph Huber via All-commits all-commits at lists.llvm.org
Mon Mar 4 10:23:23 PST 2024


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: c996023f9a288f12f97de8e1a2b8fbb28d2ed0c3
      https://github.com/llvm/llvm-project/commit/c996023f9a288f12f97de8e1a2b8fbb28d2ed0c3
  Author: Joseph Huber <huberjn at outlook.com>
  Date:   2024-03-04 (Mon, 04 Mar 2024)

  Changed paths:
    M libc/config/baremetal/arm/headers.txt
    M libc/config/baremetal/riscv/headers.txt
    M libc/config/darwin/arm/headers.txt
    M libc/config/darwin/x86_64/headers.txt
    M libc/config/gpu/headers.txt
    M libc/config/linux/aarch64/headers.txt
    M libc/config/linux/arm/headers.txt
    M libc/config/linux/riscv/headers.txt
    M libc/config/linux/x86_64/headers.txt
    M libc/include/CMakeLists.txt
    M libc/include/llvm-libc-macros/CMakeLists.txt
    A libc/include/llvm-libc-macros/stdint-macros.h
    A libc/include/stdint.h.def
    M libc/spec/stdc.td
    M utils/bazel/llvm-project-overlay/libc/BUILD.bazel

  Log Message:
  -----------
  [libc] Provide an implementation of the 'stdint.h' header (#83353)

Summary:
I've noticed one problem is that the user includes `stdint.h` the
compiler will do `#include_next <stdint.h>` potentially into a
conflicting implementation on systems with multiple headers installed.
The `clang` header is standards compliant and works with `clang` and
`gcc` which are both of our targets, so I simply copied it here. This
has the effect of including `stdint.h` on clang / LLVM libc behaving the
same as `-ffreestanding`.



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


More information about the All-commits mailing list