| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Add dladdr to dlfcn.h (#149872) A initial commit for #97929, this adds a stub implementation for dladdr and includes the definition for the DL_info type used as one of its arguments. While the dladdr implementation relies on dynamic linker support, this patch will add its prototype in the generated dlfcn.h header so that it can be used by downstream platforms that have their own dladdr implementation. | 11 个月前 | |
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
[libc][uefi] add crt1 (#132150) Adds crt1.o for the UEFI platform in the LLVM C library. This makes things start to become useful. | 1 年前 | |
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
[libc] Add struct entry definition in addition to ENTRY according to POSIX. (#139773) | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Add VISIT enum for search.h (#132746) This patch introduces the VISIT enum for tree search. Existing tests ensure the correct generation of headers. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
Add <stdbool.h> to llvm-libc-types headers that need it. (#165798) We need <stdbool.h> to support having "bool" members inside pthread structs that may get included through <pthread.h> from C code prior to C23. | 9 个月前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Define (stub) dl_iterate_phdr (#131436) This fleshes out the <link.h> a little more, including the struct dl_phdr_info type and declaring the dl_iterate_phdr function. There is only a no-op implementation without tests, as for the existing dlfcn functions. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Fix issue with sigjmp_buf.h not being found (#150439) When trying to use <setjmp.h>, it will try to include llvm-libc-types/sigjmp_buf.h due to the way that headergen works. This commit creates a dummy file, as the real implementation is found in llvm-libc-types/jmp_buf.h. | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
| 1 年前 | ||
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[NFC] Fix a comment for cfloat128.h (#157093) | 10 个月前 | |
[libc] Implement CMPLX related macros (#156344) | 10 个月前 | |
Add basic char*_t support for libc (partial WG14 N2653) (#90360) This PR implements a part of WG14 N2653: - Define C23 char8_t - Define C11 char16_t - Define C11 char32_t Missing goals are: - The type of UTF-8 character literals is changed from unsigned char to char8_t. (Since UTF-8 character literals already have type unsigned char, this is not a semantic change). - New mbrtoc8() and c8rtomb() functions declared in <uchar.h> enable conversions between multibyte characters and UTF-8. - A new ATOMIC_CHAR8_T_LOCK_FREE macro. - A new atomic_char8_t typedef name. | 2 年前 | |
Add basic char*_t support for libc (partial WG14 N2653) (#90360) This PR implements a part of WG14 N2653: - Define C23 char8_t - Define C11 char16_t - Define C11 char32_t Missing goals are: - The type of UTF-8 character literals is changed from unsigned char to char8_t. (Since UTF-8 character literals already have type unsigned char, this is not a semantic change). - New mbrtoc8() and c8rtomb() functions declared in <uchar.h> enable conversions between multibyte characters and UTF-8. - A new ATOMIC_CHAR8_T_LOCK_FREE macro. - A new atomic_char8_t typedef name. | 2 年前 | |
[libc] Build fixes for widechar characterconverter (#143805) Build fixes for wchar CharacterConverter class | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
| 1 年前 | ||
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Fix fexcept_t type to match canonical ABI and API (#113666) In glibc and musl, fexcept_t is unsigned short int on x86 and unsigned int on other machines that llvm-libc supports. Match that ABI (only different from before on x86) and API (different everywhere as it was previously signed). | 1 年前 | |
| 2 年前 | ||
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Change fsfilcnt_t and fsblkcnt_t to be 64-bits long (#99876) In 32-bit systems with 64-bit offsets, both fsfilcnt_t and fsblkcnt_t are 64-bit long, just like 64-bit systems. This patch changes both types to be 64-bit long for all platforms and follows the reasoning used to change off_t: the standard only requires it to be an unsigned int, so making it 64-bit long doesn't violate this property. It should be NFC for 64-bit systems. | 2 年前 | |
[libc] Change fsfilcnt_t and fsblkcnt_t to be 64-bits long (#99876) In 32-bit systems with 64-bit offsets, both fsfilcnt_t and fsblkcnt_t are 64-bit long, just like 64-bit systems. This patch changes both types to be 64-bit long for all platforms and follows the reasoning used to change off_t: the standard only requires it to be an unsigned int, so making it 64-bit long doesn't violate this property. It should be NFC for 64-bit systems. | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Move the remaining public types to their own type headers. Reviewed By: michaelrj Differential Revision: https://reviews.llvm.org/D117838 | 4 年前 | |
[libc] add in_addr{, _t} type (#162452) These types will be used in arpa/inet.h and netinet/in.h. | 9 个月前 | |
[libc] add in_addr{, _t} type (#162452) These types will be used in arpa/inet.h and netinet/in.h. | 9 个月前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] Fix issue with sigjmp_buf.h not being found (#150439) When trying to use <setjmp.h>, it will try to include llvm-libc-types/sigjmp_buf.h due to the way that headergen works. This commit creates a dummy file, as the real implementation is found in llvm-libc-types/jmp_buf.h. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Initial support for 'locale.h' in the LLVM libc (#102689) Summary: This patch adds the macros and entrypoints associated with the locale.h entrypoints. These are mostly stubs, as we (for now and the forseeable future) only expect to support the C and maybe C.UTF-8 locales in the LLVM libc. | 1 年前 | |
[libc] mbrtowc implementation (#144760) implemented the internal and public mbrtowc as well as tests for the public function. --------- Co-authored-by: Sriya Pratipati <sriyap@google.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
| 1 年前 | ||
[libc] Stub out message catalog functions from <nl_types.h> (#164360) Create a POSIX <nl_types.h> header with catopen, catclose, and catgets function declarations. Provide the stub/placeholder implementations which always return error. This is consistent with the way locales are currently (un-)implemented in llvm-libc. Notably, providing <nl_types.h> fixes the last remaining issue with building libc++ against llvm-libc (on certain configuration of x86_64 Linux) after disabling threads and wide-characters in libc++. | 9 个月前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
| 1 年前 | ||
Add <stdbool.h> to llvm-libc-types headers that need it. (#165798) We need <stdbool.h> to support having "bool" members inside pthread structs that may get included through <pthread.h> from C code prior to C23. | 9 个月前 | |
| 2 年前 | ||
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
Reland: [libc][POSIX][pthreads] implemented missing pthread_rwlockattr functions (#93622) New pull request for https://github.com/llvm/llvm-project/issues/89443 The previous PR was reverted after breaking fullbuild due to a missing struct declaration, which I forgot to commit. Reverts revert and adds the missing pthread_rwlockattr_getkind_np / pthread_rwlockattr_setkind_np functions and tests respecitvely. | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc][signal] clean up usage of sighandler_t (#125745) man 3 signal's declaration has a face _only a mother could love_. sighandler_t and __sighandler_t are not defined in the C standard, or POSIX. They are helpful typedefs provided by glibc and the Linux kernel UAPI headers respectively since working with function pointers' syntax can be painful. But we should not rely on them; in C++ we have auto* and using statements. Remove the proxy header, and only include a typedef for sighandler_t when targeting Linux, for compatibility with glibc. Fixes: #125598 | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Fix issue with sigjmp_buf.h not being found (#150439) When trying to use <setjmp.h>, it will try to include llvm-libc-types/sigjmp_buf.h due to the way that headergen works. This commit creates a dummy file, as the real implementation is found in llvm-libc-types/jmp_buf.h. | 1 年前 | |
[libc] Fix sigset_t type definition (#123277) The libc headers are C, not C++. | 1 年前 | |
[libc] Update size_t and ssize_t definitions to use __SIZE_TYPE__ and __PTRDIFF_TYPE__ respectively. (#143921) The current definition of ssize_t does not have the same bit width as size_t on 32-bit platforms. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Update size_t and ssize_t definitions to use __SIZE_TYPE__ and __PTRDIFF_TYPE__ respectively. (#143921) The current definition of ssize_t does not have the same bit width as size_t on 32-bit platforms. | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Define (stub) dl_iterate_phdr (#131436) This fleshes out the <link.h> a little more, including the struct dl_phdr_info type and declaring the dl_iterate_phdr function. There is only a no-op implementation without tests, as for the existing dlfcn functions. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Add functions to send/recv messages (#106467) This patch adds the necessary functions to send and receive messages over a socket. Those functions are: recv, recvfrom, recvmsg, send, sendto, sendmsg, and socketpair for testing. | 1 年前 | |
| 1 年前 | ||
[libc] Initial support for 'locale.h' in the LLVM libc (#102689) Summary: This patch adds the macros and entrypoints associated with the locale.h entrypoints. These are mostly stubs, as we (for now and the forseeable future) only expect to support the C and maybe C.UTF-8 locales in the LLVM libc. | 1 年前 | |
[libc] Add functions to send/recv messages (#106467) This patch adds the necessary functions to send and receive messages over a socket. Those functions are: recv, recvfrom, recvmsg, send, sendto, sendmsg, and socketpair for testing. | 1 年前 | |
| 1 年前 | ||
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc][signal] clean up usage of sighandler_t (#125745) man 3 signal's declaration has a face _only a mother could love_. sighandler_t and __sighandler_t are not defined in the C standard, or POSIX. They are helpful typedefs provided by glibc and the Linux kernel UAPI headers respectively since working with function pointers' syntax can be painful. But we should not rely on them; in C++ we have auto* and using statements. Remove the proxy header, and only include a typedef for sighandler_t when targeting Linux, for compatibility with glibc. Fixes: #125598 | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Fix headers for statvfs implementation Summry: @lntue | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] create TimeReader to look at a struct tm (#126138) In the process of adding strftime (#122556) I wrote this utility class to simplify reading from a struct tm. It provides helper functions that return basically everything needed by strftime. It's not tested directly, but it is thoroughly exercised by the strftime tests. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Fix suseconds_t definition and utimes_test (#134326) The main issue was that the kernel expected suseconds_t to be 64 bits but ours was 32. This caused inconsistent failures since all valid suseconds_t values are less than 1000000 (1 million), and some configurations caused struct timeval to be padded to 128 bits. Also: forgot to use TEST_FILE instead of FILE_PATH in some places. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Use relative inclusion for public headers. (#114324) We are finalizing the header inclusion policy, and for our public headers in the libc/include folder, they must use relative path in "..." when including each other. This PR does the cleanup making sure that all the public header inclusions in libc/include folder use relative paths. --------- Co-authored-by: Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 1 年前 | |
[libc] Make use of 32-bit time_t a config option (#102012) The 32-bit Arm builds of libc define time_t to be __INTPTR_TYPE__, i.e. a 32-bit integer. This is commented in the commit introducing it (75398f28ebdb600) as being for compatibility with glibc. But in the near future not even every AArch32 build of glibc will have a 32-bit time_t: Debian is planning that their next release (trixie) will have switched to 64-bit. And non-Linux builds of this libc (e.g. baremetal) have no reason to need glibc compatibility in the first place – and every reason _not_ to want to start using a 32-bit time_t in 2024 or later. So I've replaced the #ifdef in llvm-libc-types/time_t.h with two versions of the header file, chosen in CMakeLists.txt via a new configuration option. This involved adding an extra parameter to the cmake add_header function to specify different names for the header file in the source and destination directories. | 1 年前 | |
[libc] Make use of 32-bit time_t a config option (#102012) The 32-bit Arm builds of libc define time_t to be __INTPTR_TYPE__, i.e. a 32-bit integer. This is commented in the commit introducing it (75398f28ebdb600) as being for compatibility with glibc. But in the near future not even every AArch32 build of glibc will have a 32-bit time_t: Debian is planning that their next release (trixie) will have switched to 64-bit. And non-Linux builds of this libc (e.g. baremetal) have no reason to need glibc compatibility in the first place – and every reason _not_ to want to start using a 32-bit time_t in 2024 or later. So I've replaced the #ifdef in llvm-libc-types/time_t.h with two versions of the header file, chosen in CMakeLists.txt via a new configuration option. This involved adding an extra parameter to the cmake add_header function to specify different names for the header file in the source and destination directories. | 1 年前 | |
[libc] Make use of 32-bit time_t a config option (#102012) The 32-bit Arm builds of libc define time_t to be __INTPTR_TYPE__, i.e. a 32-bit integer. This is commented in the commit introducing it (75398f28ebdb600) as being for compatibility with glibc. But in the near future not even every AArch32 build of glibc will have a 32-bit time_t: Debian is planning that their next release (trixie) will have switched to 64-bit. And non-Linux builds of this libc (e.g. baremetal) have no reason to need glibc compatibility in the first place – and every reason _not_ to want to start using a 32-bit time_t in 2024 or later. So I've replaced the #ifdef in llvm-libc-types/time_t.h with two versions of the header file, chosen in CMakeLists.txt via a new configuration option. This involved adding an extra parameter to the cmake add_header function to specify different names for the header file in the source and destination directories. | 1 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] add missing headers in stdfix (#162078) Fixes https://github.com/llvm/llvm-project/issues/129361 @michaelrj-google @PiJoules --------- Signed-off-by: Shreeyash Pandey <shreeyash335@gmail.com> Co-authored-by: Michael Jones <michaelrj@google.com> | 9 个月前 | |
[libc] fix clang-tidy llvm-header-guard warnings (#82679) Towards the goal of getting ninja libc-lint back to green, fix the numerous instances of: warning: header guard does not follow preferred style [llvm-header-guard] This is because many of our header guards start with __LLVM rather than LLVM. To filter just these warnings: $ ninja -k2000 libc-lint 2>&1 | grep llvm-header-guard To automatically apply fixits: $ find libc/src libc/include libc/test -name \*.h | \ xargs -n1 -I {} clang-tidy {} -p build/compile_commands.json \ -checks='-*,llvm-header-guard' --fix --quiet Some manual cleanup is still necessary as headers that were missing header guards outright will have them inserted before the license block (we prefer them after). | 2 年前 | |
[libc] Do not redefine wchar_t when compiling in C++ (#110769) Summary: This is a fundamental type in C++, so we can't redefine it. | 1 年前 | |
[libc][wchar] Move wchar's types to proxy headers. (#109334) Also protect against extern inline function definitions added when building with gcc: https://github.com/llvm/llvm-project/issues/60481. | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 |