| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[libc++][tests] Use CMake provided paths for includes and libdir instead of hardcoding them In the new-style testing configurations, we were hardcoding paths to the include and lib directories, which was incorrect but always went unnoticed because the hardcoded values always happened to match the actual value. When using new-style configs with the bootstrapping build, this falls appart -- and we never noticed this because the bootstrapping build was still using old style configs. This patch removes the %{install} substitution, which makes it too tempting to hardcode installation paths, and it also switches the bootstrapping build to actually using new-style configs like we always intended to do. Differential Revision: https://reviews.llvm.org/D121700 | 4 年前 | |
[libc++][tests] Use CMake provided paths for includes and libdir instead of hardcoding them In the new-style testing configurations, we were hardcoding paths to the include and lib directories, which was incorrect but always went unnoticed because the hardcoded values always happened to match the actual value. When using new-style configs with the bootstrapping build, this falls appart -- and we never noticed this because the bootstrapping build was still using old style configs. This patch removes the %{install} substitution, which makes it too tempting to hardcode installation paths, and it also switches the bootstrapping build to actually using new-style configs like we always intended to do. Differential Revision: https://reviews.llvm.org/D121700 | 4 年前 | |
[libunwind] Introduce a cmake-bridge.cfg.in file to reduce test config duplication Differential Revision: https://reviews.llvm.org/D125981 | 4 年前 | |
[libcxx][AIX] Switch build compiler to clang This patch switches the build compiler for AIX from ibm-clang to clang. ibm-clang++_r has -pthread by default, but clang for AIX doesn't, so -pthread had to be added to the test config. A bunch of tests now pass, so the XFAIL was removed. This patch also switch the build to use the visibility support available in clang-15 to control symbols exported by the shared library (AIX traditionally uses explicit export lists for this purpose). Reviewed By: #libc, #libc_abi, daltenty, #libunwind, ldionne Differential Revision: https://reviews.llvm.org/D127470 | 4 年前 | |
[runtimes] Officially deprecate the legacy testing configuration system Add a warning and tweak the release note to explain that the deprecation targets libc++, libc++abi and libuwnind as well. Also, as a fly-by, ensure that our CI runs the legacy testing configuration for libc++, libc++abi and libunwind. This doesn't matter too much since it's deprecated, but we might as well test it properly. Differential Revision: https://reviews.llvm.org/D126478 | 4 年前 | |
[libcxx] [test] Stop defining LIBCXX-WINDOWS-FIXME There are no such markings left - all of them have been fixed or analyzed. This closes llvm.org/PR32730 (github issue #32077). Differential Revision: https://reviews.llvm.org/D123145 | 4 年前 | |
[libcxx] [test] Stop defining LIBCXX-WINDOWS-FIXME There are no such markings left - all of them have been fixed or analyzed. This closes llvm.org/PR32730 (github issue #32077). Differential Revision: https://reviews.llvm.org/D123145 | 4 年前 | |
[libc++] Use -I instead of -isystem to include headers in the test suite Using -isystem marks the headers as system headers, which means that we don't actually get all the warnings that we'd normally get if we included the headers as user headers. The goal of the test suite is normally to mirror as closely as possible how users would use the library. Technically, this change goes against that philosophy, since users should be using -isystem (if they ever need to specify the libc++ path explicitly, which should be a rare occurence). However, I believe fishing out additional warnings from the headers provides more value, hence this change. Ideally, we'd be able to still use -isystem, but instruct Clang to still emit warnings from the libc++ headers (e.g. we could tell Clang to emit warnings in any file inside <...>/usr/include/c++/v1). Reviewed By: #libc, ldionne, #libc_abi Spies: Mordante, EricWF, mstorsjo, mgorny, aheejin, arichardson, philnik, jloser, libcxx-commits Differential Revision: https://reviews.llvm.org/D118616 | 4 年前 | |
[libc++] Use -I instead of -isystem to include headers in the test suite Using -isystem marks the headers as system headers, which means that we don't actually get all the warnings that we'd normally get if we included the headers as user headers. The goal of the test suite is normally to mirror as closely as possible how users would use the library. Technically, this change goes against that philosophy, since users should be using -isystem (if they ever need to specify the libc++ path explicitly, which should be a rare occurence). However, I believe fishing out additional warnings from the headers provides more value, hence this change. Ideally, we'd be able to still use -isystem, but instruct Clang to still emit warnings from the libc++ headers (e.g. we could tell Clang to emit warnings in any file inside <...>/usr/include/c++/v1). Reviewed By: #libc, ldionne, #libc_abi Spies: Mordante, EricWF, mstorsjo, mgorny, aheejin, arichardson, philnik, jloser, libcxx-commits Differential Revision: https://reviews.llvm.org/D118616 | 4 年前 | |
[libcxx] [test] Stop defining LIBCXX-WINDOWS-FIXME There are no such markings left - all of them have been fixed or analyzed. This closes llvm.org/PR32730 (github issue #32077). Differential Revision: https://reviews.llvm.org/D123145 | 4 年前 | |
[libc++] Use -I instead of -isystem to include headers in the test suite Using -isystem marks the headers as system headers, which means that we don't actually get all the warnings that we'd normally get if we included the headers as user headers. The goal of the test suite is normally to mirror as closely as possible how users would use the library. Technically, this change goes against that philosophy, since users should be using -isystem (if they ever need to specify the libc++ path explicitly, which should be a rare occurence). However, I believe fishing out additional warnings from the headers provides more value, hence this change. Ideally, we'd be able to still use -isystem, but instruct Clang to still emit warnings from the libc++ headers (e.g. we could tell Clang to emit warnings in any file inside <...>/usr/include/c++/v1). Reviewed By: #libc, ldionne, #libc_abi Spies: Mordante, EricWF, mstorsjo, mgorny, aheejin, arichardson, philnik, jloser, libcxx-commits Differential Revision: https://reviews.llvm.org/D118616 | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 |