summaryrefslogtreecommitdiffstats
path: root/compiler-rt/lib/builtins/i386
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Revert 1689ad27af5 "[builtins] Implement rounding mode support for ↵Yi Kong2019-11-271-0/+39
| | | | | | | | | i386/x86_64"" Don't build specilised fp_mode.c on MSVC since it does not support inline ASM on x86_64. This reverts commit a19f0eec94e195cac676d0d473882b48f4fded90.
* Revert 1689ad27af5 "[builtins] Implement rounding mode support for i386/x86_64"Hans Wennborg2019-11-191-39/+0
| | | | | | | | It broke the build with MSVC: fp_mode.c(20): error C2065: '__asm__': undeclared identifier > Differential Revision: https://reviews.llvm.org/D69870
* [builtins] Implement rounding mode support for i386/x86_64Yi Kong2019-11-181-0/+39
| | | | Differential Revision: https://reviews.llvm.org/D69870
* [builtins] Use single line C++/C99 comment stylePetr Hosek2019-04-288-77/+77
| | | | | | | | | | | Use the uniform single line C++/99 style for code comments. This is part of the cleanup proposed in "[RFC] compiler-rt builtins cleanup and refactoring". Differential Revision: https://reviews.llvm.org/D60352 llvm-svn: 359411
* Update more file headers across all of the LLVM projects in the monorepoChandler Carruth2019-01-1916-34/+48
| | | | | | | | | | | | | | | | | | to reflect the new license. These used slightly different spellings that defeated my regular expressions. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351648
* Delete remaining compiler-rt makefilesChris Bieneman2016-08-231-20/+0
| | | | | | | | | | | | | | | Summary: Since we can now build the builtins without a full toolchain these files should no longer be needed. This is the last vestige of autoconf! Reviewers: compnerd, iains, jroelofs Subscribers: dberris, llvm-commits Differential Revision: https://reviews.llvm.org/D23777 llvm-svn: 279539
* builtins: tag with noexecstackSaleem Abdulrasool2016-06-2214-0/+42
| | | | | | | | | | | | These routines do not require executable stacks. However, by default ELFish linkers may assume an executable stack on GNUish environments (and some non-GNU ones too!). The GNU extension to add a note to indicate a non-executable stack is honoured by these environments to mark the stack as non-executable (the compiler normally emits this directive on appropriate targets whenever possible). This allows normal builds from getting executable stacks due to linking to the compiler rt builtins. llvm-svn: 273500
* Support for 32-bit mingw-w64 in compiler-rt.Martell Malone2015-11-032-2/+42
| | | | | | | | | | | | Add chkstk/alloca for gcc objects. Replace or instructions with test, the latter should be marginally more efficent, as it does not write to memory. Differential Revision: http://reviews.llvm.org/D14044 Patch by vadimcn llvm-svn: 251928
* Add missing chkstk.S files from r242539Reid Kleckner2015-07-171-0/+34
| | | | llvm-svn: 242540
* builtins: cleanup constant data section selectionSaleem Abdulrasool2014-12-104-29/+5
| | | | | | | | | | Each of the object formats use a different directive for selecting the constant section. Use a macro to avoid the duplication across a number of files. Also correct a small macro mismatch on the Windows case (HIDDEN_DIRECTIVE -> HIDDEN). Patch by Vadim Chugunov! llvm-svn: 223910
* builtins: add missed files from previous commitsSaleem Abdulrasool2014-07-261-1/+1
| | | | | | | This adds missed files in SVN r214033 for alignment and corrects a change from SVN r214034 for fixing compilation with GCC. llvm-svn: 214039
* builtins: move the readonly constants into rodataSaleem Abdulrasool2014-07-264-8/+27
| | | | | | | Place the floating point constants into the read-only data section. This was already being done for x86_64, this simply mirrors the behaviour for i686. llvm-svn: 214034
* builtins: correct constant alignmentsSaleem Abdulrasool2014-07-264-17/+41
| | | | | | | | | | | | | | | | | | | MMX/SSE instructions expect 128-bit alignment (16-byte) for constants that they reference. Correct the alignment on the constant values. Although it is quite possible for the data to end up aligned, there is no guarantee that this will occur unless it is explicitly aligned to the desired location. If the data ends up being unaligned, the resultant binary would fault at runtime due to the unaligned access. As an example, the follow would fault previously: cc -c lib/builtins/x86_64/floatundidf.S -o floatundidf.o cc -c test/builtins/Unit/floatundidf_test.c -o floatundidf_test.c ld -m elf_x86_64 floatundidf.o floatundidf_test.o -lc -o floatundidf However, if the object files were reversed, the data would end up aligned and the problem would go unnoticed. llvm-svn: 214033
* CompilerRT: .align was supposed to be power-of-aligned in this caseSaleem Abdulrasool2014-05-121-3/+1
| | | | | | Use .balign instead of .p2align 3. This should fix the buildbots. llvm-svn: 208585
* [CompilerRT] use .p2align, .balign instead of .alignSaleem Abdulrasool2014-05-1214-24/+24
| | | | | | | | | | | | The .align statements in ARM assembly routines is actually meant to be a power of 2 alignment (e.g. .align 2 == 4 byte alignment, not 2). Switch to using .p2align. .p2align is guaranteed to be a power-of-two alignment always and much more explicit. The .align in the case of x86_64 is byte alignment, use .balign instead of .align. llvm-svn: 208578
* Move original compiler-rt functions (libgcc replacement) to lib/builtins ↵Alexey Samsonov2014-02-1415-0/+1089
directory llvm-svn: 201393
OpenPOWER on IntegriCloud