llvm-project

History

[llvm][Support] Put back filename into FileToRemoveList (#124065 )

Prevents avoidable memory leaks.

Looks like exchange added in aa1333a91f8d8a060bcf5b14aa32a6e8bab74e8c
didn't take "continue" into account.

```
==llc==2150782==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 10 byte(s) in 1 object(s) allocated from:
    #0 0x5f1b0f9ac14a in strdup llvm-project/compiler-rt/lib/asan/asan_interceptors.cpp:593:3
    #1 0x5f1b1768428d in FileToRemoveList llvm-project/llvm/lib/Support/Unix/Signals.inc:105:55
```

2025-01-23 03:57:19 -08:00

COM.inc

…

DynamicLibrary.inc

[CMake] Remove HAVE_DLFCN_H and HAVE_DLADDR (#123879 )

2025-01-22 08:15:10 -08:00

Memory.inc

…

Path.inc

[CMake] Remove HAVE_DLFCN_H and HAVE_DLADDR (#123879 )

2025-01-22 08:15:10 -08:00

Process.inc

[CMake] Remove HAVE_SYS_RESOURCE_H/HAVE_SETRLIMIT/HAVE_GETRLIMIT

2025-01-16 22:44:54 -08:00

Program.inc

[CMake] Remove HAVE_SYS_RESOURCE_H/HAVE_SETRLIMIT/HAVE_GETRLIMIT

2025-01-16 22:44:54 -08:00

README.txt

…

Signals.inc

[llvm][Support] Put back filename into FileToRemoveList (#124065 )

2025-01-23 03:57:19 -08:00

Threading.inc

[llvm][Support] Use __NR_gettid on Linux for compat with older glibc (#120007 )

2024-12-18 16:19:09 -05:00

Unix.h

[CMake] Remove HAVE_DLFCN_H and HAVE_DLADDR (#123879 )

2025-01-22 08:15:10 -08:00

Watchdog.inc

…

README.txt

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.