[libc++] [libc++abi] Mark a few tests as unsupported/xfail on gcc-7/8/9.This should make the builder http://lab.llvm.org:8011/#/builders/101/ happy.It uses gcc-9 and not Tip-Of-Trunk as its name i
[libc++] [libc++abi] Mark a few tests as unsupported/xfail on gcc-7/8/9.This should make the builder http://lab.llvm.org:8011/#/builders/101/ happy.It uses gcc-9 and not Tip-Of-Trunk as its name indicates BTW.GCC-10 passes all these tests.Fix gcc warnings: -Wsign-compare, -Wparentheses, -Wpragmas.Reviewed By: ldionne, #libc, #libc_abiDifferential Revision: https://reviews.llvm.org/D92099
show more ...
[libc++] Remove the c++98 Lit feature from the test suiteC++98 and C++03 are effectively aliases as far as Clang is concerned.As such, allowing both std=c++98 and std=c++03 as Lit parameters isju
[libc++] Remove the c++98 Lit feature from the test suiteC++98 and C++03 are effectively aliases as far as Clang is concerned.As such, allowing both std=c++98 and std=c++03 as Lit parameters isjust slightly confusing, but provides no value. It's similar to allowingboth std=c++17 and std=c++1z, which we don't do.This was discovered because we had an internal bot that ran the testsuite under both c++98 AND c++03 -- one of which is redundant.Differential Revision: https://reviews.llvm.org/D80926
[libcxx] Do not implicitly #include assert.hUsers should only get the assert() macros if they explicitly includethem.Found after switching from the GNU C++ stdlib to the LLVM C++ stdlib.llvm-s
[libcxx] Do not implicitly #include assert.hUsers should only get the assert() macros if they explicitly includethem.Found after switching from the GNU C++ stdlib to the LLVM C++ stdlib.llvm-svn: 372963
[libc++] Purge mentions of GCC 4 from the test suiteWe don't support GCC 4 and older according to the documentation, sowe should pretend it doesn't exist.This is a re-application of r372787.ll
[libc++] Purge mentions of GCC 4 from the test suiteWe don't support GCC 4 and older according to the documentation, sowe should pretend it doesn't exist.This is a re-application of r372787.llvm-svn: 372916
Revert r372777: [libc++] Implement LWG 2510 and its follow-upsThis also reverts: - r372778: [libc++] Implement LWG 3158 - r372782: [libc++] Try fixing tests that fail on GCC 5 and older - r37278
Revert r372777: [libc++] Implement LWG 2510 and its follow-upsThis also reverts: - r372778: [libc++] Implement LWG 3158 - r372782: [libc++] Try fixing tests that fail on GCC 5 and older - r372787: Purge mentions of GCC 4 from the test suiteReason: the change breaks compilation of LLVM with libc++, for details seehttp://lists.llvm.org/pipermail/libcxx-dev/2019-September/000599.htmlllvm-svn: 372832
[libc++] Purge mentions of GCC 4 from the test suiteWe don't support GCC 4 and older according to the documentation, sowe should pretend it doesn't exist.llvm-svn: 372787
Add include for 'test_macros.h' to all the tests that were missing them. Thanks to Zoe for the (big, but simple) patch. NFC intended.llvm-svn: 362252
Support tests in freestandingSummary:Freestanding is *weird*. The standard allows it to differ in a bunch of oddmanners from regular C++, and the committee would like to improve thatsituation. I
Support tests in freestandingSummary:Freestanding is *weird*. The standard allows it to differ in a bunch of oddmanners from regular C++, and the committee would like to improve thatsituation. I'd like to make libc++ behave better with what freestanding shouldbe, so that it can be a tool we use in improving the standard. To do that weneed to try stuff out, both with "freestanding the language mode" and"freestanding the library subset".Let's start with the super basic: run the libc++ tests in freestanding, usingclang as the compiler, and see what works. The easiest hack to do this:In utils/libcxx/test/config.py add: self.cxx.compile_flags += ['-ffreestanding']Run the tests and they all fail.Why? Because in freestanding `main` isn't special. This "not special" propertyhas two effects: main doesn't get mangled, and main isn't allowed to omit its`return` statement. The first means main gets mangled and the linker can'tcreate a valid executable for us to test. The second means we spew out warnings(ew) and the compiler doesn't insert the `return` we omitted, and main justfalls of the end and does whatever undefined behavior (if you're luck, ud2leading to non-zero return code).Let's start my work with the basics. This patch changes all libc++ tests todeclare `main` as `int main(int, char**` so it mangles consistently (enabling usto declare another `extern "C"` main for freestanding which calls the mangledone), and adds `return 0;` to all places where it was missing. This touches 6124files, and I apologize.The former was done with The Magic Of Sed.The later was done with a (not quite correct but decent) clang tool: https://gist.github.com/jfbastien/793819ff360baa845483dde81170feedThis works for most tests, though I did have to adjust a few places when e.g.the test runs with `-x c`, macros are used for main (such as for the filesystemtests), etc.Once this is in we can create a freestanding bot which will prevent furtherregressions. After that, we can start the real work of supporting C++freestanding fairly well in libc++.<rdar://problem/47754795>Reviewers: ldionne, mclow.lists, EricWFSubscribers: christof, jkorous, dexonsmith, arphaman, miyuki, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D57624llvm-svn: 353086
Update more file headers across all of the LLVM projects in the monorepoto reflect the new license. These used slightly different spellings thatdefeated my regular expressions.We understand that
Update more file headers across all of the LLVM projects in the monorepoto reflect the new license. These used slightly different spellings thatdefeated my regular expressions.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351648
Fix UB in SIMD tests.One of the SIMD tests attempted to left shift a value by 42, whichis UB when the left hand side is a 32 bit integer type.This patch adjusts the test to use the value 4 inste
Fix UB in SIMD tests.One of the SIMD tests attempted to left shift a value by 42, whichis UB when the left hand side is a 32 bit integer type.This patch adjusts the test to use the value 4 instead of 42.llvm-svn: 342820
[libcxx] fix `>> 42` UB in <experimental/simd>llvm-svn: 338325
Re-apply "[libcxx] implement <simd> ABI for Clang/GCC vector extension, constructors, copy_from and copy_to."...with proper guarding #ifdefs for unsupported C++11.llvm-svn: 338318
Revert "[libcxx] implement <simd> ABI for Clang/GCC vector extension, constructors, copy_from and copy_to."This reverts commit r338309.llvm-svn: 338316
[libcxx] implement <simd> ABI for Clang/GCC vector extension, constructors, copy_from and copy_to.Summary:This patch adds a new macro _LIBCPP_HAS_NO_VECTOR_EXTENSION for detectingwhether a vector
[libcxx] implement <simd> ABI for Clang/GCC vector extension, constructors, copy_from and copy_to.Summary:This patch adds a new macro _LIBCPP_HAS_NO_VECTOR_EXTENSION for detectingwhether a vector extension (\_\_attribute\_\_((vector_size(num_bytes)))) isavailable.On the top of that, this patch implements the following API:* all constructors* operator[]* copy_from* copy_toIt also defines simd_abi::native to use vector extension, if available.In GCC and Clang, certain values with vector extension are passed by registers,instead of memory.Based on D41148.Reviewers: mclow.lists, EricWFSubscribers: cfe-commits, MaskRay, lichray, sanjoyDifferential Revision: https://reviews.llvm.org/D41376llvm-svn: 338309
Re-commit r330627 "[libcxx] implement <experimental/simd> declarations based on P0214R7."There are 3 changes:* Renamed genertor.pass.cpp to generator.pass.cpp* Removed nothing_to_do.pass.cpp* Ma
Re-commit r330627 "[libcxx] implement <experimental/simd> declarations based on P0214R7."There are 3 changes:* Renamed genertor.pass.cpp to generator.pass.cpp* Removed nothing_to_do.pass.cpp* Mark GCC 4.9 as UNSUPPORTED for the test files that have negative narrowing conversion SFINAE test (see GCC PR63723).llvm-svn: 330655
Revert "[libcxx] implement <experimental/simd> declarations based on P0214R7."This reverts commit r330627.This causes several bots to freak out.llvm-svn: 330636
[libcxx] implement <experimental/simd> declarations based on P0214R7.Summary:The patch includes all declarations, and also implements the following features:* ABI.* narrowing-conversion related
[libcxx] implement <experimental/simd> declarations based on P0214R7.Summary:The patch includes all declarations, and also implements the following features:* ABI.* narrowing-conversion related SFIANE, including simd<> ctors and (static_)simd_cast.Reviewers: mclow.lists, EricWFSubscribers: lichray, sanjoy, MaskRay, cfe-commitsDifferential Revision: https://reviews.llvm.org/D41148llvm-svn: 330627