llvm-project/libc/include/stdint.h.def

//===-- C standard library header stdint.h --------------------------------===//
//
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
// See https://llvm.org/LICENSE.txt for license information.
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
//
//===----------------------------------------------------------------------===//

#ifndef LLVM_LIBC_STDINT_H
#define LLVM_LIBC_STDINT_H

#include "llvm-libc-macros/stdint-macros.h"

#endif // LLVM_LIBC_STDINT_H
[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`. 2024-03-04 12:23:11 -06:00			`//===-- C standard library header stdint.h --------------------------------===//`
			`//`
			`// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.`
			`// See https://llvm.org/LICENSE.txt for license information.`
			`// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception`
			`//`
			`//===----------------------------------------------------------------------===//`

			`#ifndef LLVM_LIBC_STDINT_H`
			`#define LLVM_LIBC_STDINT_H`

[libc] fix up the use of angle includes in include/ (#86027) 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 2024-03-22 08:24:08 -07:00			`#include "llvm-libc-macros/stdint-macros.h"`
[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`. 2024-03-04 12:23:11 -06:00
			`#endif // LLVM_LIBC_STDINT_H`