llvm-project.git/libc/include/stdint.h.def, branch users/nico/python-1 Unnamed repository; edit this file 'description' to name the repository. [libc] fix up the use of angle includes in include/ (#86027) 2024-03-22T15:24:08+00:00 Nick Desaulniers nickdesaulniers@users.noreply.github.com 2024-03-22T15:24:08+00:00 cdbec7baf1bc31b59526442c9d4d5f53aac746eb Performed en-masse via: $ grep -rn "#include <ll" libc/include -l | \ xargs perl -pi -e 's/#include <ll(.*)>/#include "ll$1"/' $ grep -rn "#include <__" libc/include -l | \ xargs perl -pi -e 's/#include <__(.*)>/#include "__$1"/' Link: #83463 Link: #83210 
Performed en-masse via:

    $ grep -rn "#include <ll" libc/include -l | \
      xargs perl -pi -e 's/#include <ll(.*)>/#include "ll$1"/'
    $ grep -rn "#include <__" libc/include -l | \
      xargs perl -pi -e 's/#include <__(.*)>/#include "__$1"/'

Link: #83463
Link: #83210
[libc] Provide an implementation of the 'stdint.h' header (#83353) 2024-03-04T18:23:11+00:00 Joseph Huber huberjn@outlook.com 2024-03-04T18:23:11+00:00 c996023f9a288f12f97de8e1a2b8fbb28d2ed0c3 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`. 
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`.