AAaron BallmanSpeculatively fix build bots
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[builtins][ARM] Replace call_apsr.S with inline asm The %arm_call_apsr expansion doesn't work when config.clang is a clang driver defaulting to a non-ARM arch. Rather than fix it, replace call_apsr.S with inline asm in call_apsr.h, which also resolves the FIXME added in D31259. Maybe the __attribute__((noinline,pcs("aapcs"))) attributes are unnecessary on the static functions, but I was unsure what liberty the compiler had to insert instructions that modified the condition codes, so it seemed helpful. Differential Revision: https://reviews.llvm.org/D82147 | 5 年前 | |
Speculatively fix build bots This should address the issues found by: https://lab.llvm.org/buildbot/#/builders/105/builds/24292 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[clang][compiler-rt][atomics] Add __c11_atomic_fetch_nand builtin and support __atomic_fetch_nand libcall Add __c11_atomic_fetch_nand builtin to language extensions and support __atomic_fetch_nand libcall in compiler-rt. Reviewed By: theraven Differential Revision: https://reviews.llvm.org/D112400 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt] NFC: Fix trivial typo Reviewed By: xgupta Differential Revision: https://reviews.llvm.org/D77457 | 4 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
Reland "[builtins] Define fmax and scalbn inline" This reverts commit 680f836c2fa72166badd594a52b3f41b2ad074d2. Disable the non-default-rounding-mode scalbn[f] tests when we're using the MSVC libraries. Differential Revision: https://reviews.llvm.org/D91841 | 5 年前 | |
Reland "[builtins] Define fmax and scalbn inline" This reverts commit 680f836c2fa72166badd594a52b3f41b2ad074d2. Disable the non-default-rounding-mode scalbn[f] tests when we're using the MSVC libraries. Differential Revision: https://reviews.llvm.org/D91841 | 5 年前 | |
Reland "[builtins] Define fmax and scalbn inline" This reverts commit 680f836c2fa72166badd594a52b3f41b2ad074d2. Disable the non-default-rounding-mode scalbn[f] tests when we're using the MSVC libraries. Differential Revision: https://reviews.llvm.org/D91841 | 5 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Make __div[sdt]f3 handle denormal results This patch introduces denormal result support to soft-float division implementation unified by D85031. Reviewed By: sepavloff Differential Revision: https://reviews.llvm.org/D85032 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
Add __divmodti4 to match libgcc. gcc has used this on x86-64 since at least version 7. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D80506 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Make __div[sdt]f3 handle denormal results This patch introduces denormal result support to soft-float division implementation unified by D85031. Reviewed By: sepavloff Differential Revision: https://reviews.llvm.org/D85032 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt][builtins] Un-xfail two tests on sparcv9 Two tests currently XPASS on sparcv9: Unexpectedly Passed Tests (2): Builtins-sparcv9-sunos :: compiler_rt_logbl_test.c Builtins-sparcv9-sunos :: divtc3_test.c The following patch fixes this. Tested on sparcv9-sun-solaris2.11. Differential Revision: https://reviews.llvm.org/D85119 | 5 年前 | |
[builtins] Fix divtf3_test.c Fixes 93eed63d2f3188 [builtins] Make __div[sdt]f3 handle denormal results. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[VE] Disable incompatible compiler-rt tests Some compiler-rt tests are inherently incompatible with VE because.. * No consistent denormal support on VE. We skip denormal fp inputs in builtin tests. * madvise unsupported on VE. * Instruction alignment requirements. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D113093 | 4 年前 | |
[compiler-rt] Remove mentions of AuroraUX in code comments and docs. AuroraUX was an operating system project based on an OpenSolaris kernel and an Ada userland. There appear to be no public code or release available online anymore. The project page on Wikipedia [1] was deleted in January 2012, and a news item [2] from November 2012 has more details. [1] https://en.wikipedia.org/w/index.php?title=Special:Log/delete&page=AuroraUX [2] https://www.phoronix.com/scan.php?page=news_item&px=MTIyMTI | 4 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt] [builtins] Use _Float16 on extendhfsf2, truncdfhf2 __truncsfhf2 if available On AArch64 it allows use the native FP16 ABI (although libcalls are not emitted for fptrunc/fpext lowering), while on other architectures the expected current semantic is preserved (arm for instance). For testing the _Float16 usage is enabled by architecture base, currently only for arm, aarch64, and arm64. This re-enabled revert done by https://reviews.llvm.org/rGb534beabeed3ba1777cd0ff9ce552d077e496726 Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D92241 | 5 年前 | |
[compiler-rt] [builtins] Support conversion between fp16 and fp128 This patch adds both extendhftf2 and trunctfhf2 to support conversion between half-precision and quad-precision floating-point values. They are built iff the compiler supports _Float16. Some notes on ARM plaforms: while fp16 is supported on all architectures, _Float16 is supported only for 32-bit ARM, 64-bit ARM, and SPIR (as indicated by clang/docs/LanguageExtensions.rst). Also, fp16 is a storage format and 64-bit ARM supports floating-point convert precision to half as base armv8-a instruction. This patch does not change the ABI for 32-bit ARM, it will continue to pass _Float16 as uint16. This re-enabled revert done by https://reviews.llvm.org/rGb534beabeed3ba1777cd0ff9ce552d077e496726 Differential Revision: https://reviews.llvm.org/D92242 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt][builtins] Use explicitly-sized integer types for LibCalls Use s[iu]_int instead of (unsigned) int and d[ui]_int instead of (unsigned) long long for LibCall arguments. Note: the *vfp LibCall versions were NOT touched. Reviewed By: aykevl Differential Revision: https://reviews.llvm.org/D86546 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[compiler-rt][builtins] Use explicitly-sized integer types for LibCalls Use s[iu]_int instead of (unsigned) int and d[ui]_int instead of (unsigned) long long for LibCall arguments. Note: the *vfp LibCall versions were NOT touched. Reviewed By: aykevl Differential Revision: https://reviews.llvm.org/D86546 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt][builtins] Use explicitly-sized integer types for LibCalls Use s[iu]_int instead of (unsigned) int and d[ui]_int instead of (unsigned) long long for LibCall arguments. Note: the *vfp LibCall versions were NOT touched. Reviewed By: aykevl Differential Revision: https://reviews.llvm.org/D86546 | 4 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt][builtins] Use explicitly-sized integer types for LibCalls Use s[iu]_int instead of (unsigned) int and d[ui]_int instead of (unsigned) long long for LibCall arguments. Note: the *vfp LibCall versions were NOT touched. Reviewed By: aykevl Differential Revision: https://reviews.llvm.org/D86546 | 4 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt] NFC: Fix trivial typo Reviewed By: xgupta Differential Revision: https://reviews.llvm.org/D77457 | 4 年前 | |
These compiler-rt tests should be UNSUPPORTED instead of XFAIL. These compiler-rt tests should be UNSUPPORTED instead of XFAIL, which seems to be the real intent of the authors. Reviewed By: vvereschaka Differential Revision: https://reviews.llvm.org/D89840 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Replace call_apsr.S with inline asm The %arm_call_apsr expansion doesn't work when config.clang is a clang driver defaulting to a non-ARM arch. Rather than fix it, replace call_apsr.S with inline asm in call_apsr.h, which also resolves the FIXME added in D31259. Maybe the __attribute__((noinline,pcs("aapcs"))) attributes are unnecessary on the static functions, but I was unsure what liberty the compiler had to insert instructions that modified the condition codes, so it seemed helpful. Differential Revision: https://reviews.llvm.org/D82147 | 5 年前 | |
[Compiler-rt] Distinguish between testing just built runtime libraries and the libraries shipped with the compiler. The path to the runtime libraries used by the compiler under test is normally identical to the path where just built libraries are created. However, this is not necessarily the case when doing standalone builds. This is because the external compiler used by tests may choose to get its runtime libraries from somewhere else. When doing standalone builds there are two types of testing we could be doing: * Test the just built runtime libraries. * Test the runtime libraries shipped with the compile under test. Both types of testing are valid but it confusingly turns out compiler-rt actually did a mixture of these types of testing. * The test/builtins/Unit/ test suite always tested the just built runtime libraries. * All other testsuites implicitly use whatever runtime library the compiler decides to link. There is no way for us to infer which type of testing the developer wants so this patch introduces a new COMPILER_RT_TEST_STANDALONE_BUILD_LIBS CMake option which explicitly declares which runtime libraries should be tested. If it is ON then the just built libraries should be tested, otherwise the libraries in the external compiler should be tested. When testing starts the lit test suite queries the compiler used for testing to see where it will get its runtime libraries from. If these paths are identical no action is taken (the common case). If the paths are not identical then we check the value of COMPILER_RT_TEST_STANDALONE_BUILD_LIBS (progated into the config as test_standalone_build_libs) and check if the test suite supports testing in the requested configuration. * If we want to test just built libs and the test suite supports it (currently only test/builtins/Unit) then testing proceeds without any changes. * If we want to test the just built libs and the test suite doesn't support it we emit a fatal error to prevent the developer from testing the wrong runtime libraries. * If we are testing the compiler's built libs then we adjust config.compiler_rt_libdir to point at the compiler's runtime directory. This makes the test/builtins/Unit tests use the compiler's builtin library. No other changes are required because all other testsuites implicitly use the compiler's built libs. To make the above work the test_suite_supports_overriding_runtime_lib_path test suite config option has been introduced so we can identify what each test suite supports. Note all of these checks **have to be performed** when lit runs. We cannot run the checks at CMake generation time because multi-configuration build systems prevent us from knowing what the paths will be. We could perhaps support COMPILER_RT_TEST_STANDALONE_BUILD_LIBS being ON for most test suites (when the runtime library paths differs) in the future by specifiying a custom compiler resource directory path. Doing so is out of scope for this patch. rdar://77182297 Differential Revision: https://reviews.llvm.org/D101681 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[compiler-rt][builtins][RISCV] Always include __mul[sd]i3 builtin definitions The RISC-V implementations of the __mulsi3, __muldi3 builtins were conditionally compiling the actual function definitions depending on whether the M extension was present or not. This caused Compiler-RT testing failures for RISC-V targets with the M extension, as when these sources were included the librt_has_mul*i3 features were still being defined. These librt_has_* definitions are used to conditionally run the respective tests. Since the actual functions were not being compiled-in, the generic test for __muldi3 would fail. This patch makes these implementations follow the normal Compiler-RT convention of always including the definition, and conditionally running the respective tests by using the lit conditional REQUIRES: librt_has_*. Since the mulsi3_test.c wasn't actually RISC-V-specific, this patch also moves it out of the riscv directory. It now only depends on librt_has_mulsi3 to run. Differential Revision: https://reviews.llvm.org/D86457 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[compiler-rt][builtins][RISCV] Always include __mul[sd]i3 builtin definitions The RISC-V implementations of the __mulsi3, __muldi3 builtins were conditionally compiling the actual function definitions depending on whether the M extension was present or not. This caused Compiler-RT testing failures for RISC-V targets with the M extension, as when these sources were included the librt_has_mul*i3 features were still being defined. These librt_has_* definitions are used to conditionally run the respective tests. Since the actual functions were not being compiled-in, the generic test for __muldi3 would fail. This patch makes these implementations follow the normal Compiler-RT convention of always including the definition, and conditionally running the respective tests by using the lit conditional REQUIRES: librt_has_*. Since the mulsi3_test.c wasn't actually RISC-V-specific, this patch also moves it out of the riscv directory. It now only depends on librt_has_mulsi3 to run. Differential Revision: https://reviews.llvm.org/D86457 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins] Change si_int to int in some helper declarations This patch changes types of some integer function arguments or return values from si_int to the default int type to make it more compatible with libgcc. The compiler-rt/lib/builtins/README.txt has a link to the [libgcc specification](http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html#Libgcc). This specification has an explicit note on int, float and other such types being just illustrations in some cases while the actual types are expressed with machine modes. Such usage of always-32-bit-wide integer type may lead to issues on 16-bit platforms such as MSP430. Provided [libgcc2.h](https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=libgcc/libgcc2.h;hb=HEAD) can be used as a reference for all targets supported by the libgcc, this patch fixes some existing differences in helper declarations. This patch is expected to not change behavior at all for targets with 32-bit int type. Differential Revision: https://reviews.llvm.org/D81285 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
Move tests for BlocksRuntime and builtins to corresponding directories under test/ llvm-svn: 201396 | 12 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt] [builtins] Use _Float16 on extendhfsf2, truncdfhf2 __truncsfhf2 if available On AArch64 it allows use the native FP16 ABI (although libcalls are not emitted for fptrunc/fpext lowering), while on other architectures the expected current semantic is preserved (arm for instance). For testing the _Float16 usage is enabled by architecture base, currently only for arm, aarch64, and arm64. This re-enabled revert done by https://reviews.llvm.org/rGb534beabeed3ba1777cd0ff9ce552d077e496726 Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D92241 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[compiler-rt] [builtins] Use _Float16 on extendhfsf2, truncdfhf2 __truncsfhf2 if available On AArch64 it allows use the native FP16 ABI (although libcalls are not emitted for fptrunc/fpext lowering), while on other architectures the expected current semantic is preserved (arm for instance). For testing the _Float16 usage is enabled by architecture base, currently only for arm, aarch64, and arm64. This re-enabled revert done by https://reviews.llvm.org/rGb534beabeed3ba1777cd0ff9ce552d077e496726 Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D92241 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[compiler-rt] [builtins] Support conversion between fp16 and fp128 This patch adds both extendhftf2 and trunctfhf2 to support conversion between half-precision and quad-precision floating-point values. They are built iff the compiler supports _Float16. Some notes on ARM plaforms: while fp16 is supported on all architectures, _Float16 is supported only for 32-bit ARM, 64-bit ARM, and SPIR (as indicated by clang/docs/LanguageExtensions.rst). Also, fp16 is a storage format and 64-bit ARM supports floating-point convert precision to half as base armv8-a instruction. This patch does not change the ABI for 32-bit ARM, it will continue to pass _Float16 as uint16. This re-enabled revert done by https://reviews.llvm.org/rGb534beabeed3ba1777cd0ff9ce552d077e496726 Differential Revision: https://reviews.llvm.org/D92242 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][ARM] Check __ARM_FP instead of __VFP_FP__. This patch fixes builtins' CMakeLists.txt and their VFP tests to check the standard macro defined in the ACLE for VFP support. It also enables the tests to be built and run for single-precision-only targets while builtins were built with double-precision support. Differential revision: https://reviews.llvm.org/D92497 | 5 年前 | |
[builtins][test] Delete unneeded file headers We don't add file headers to tests. The comments are useless as well - their purpose can be easily inferred from the filenames. | 5 年前 |