- User Since
- Nov 6 2017, 10:05 AM (93 w, 3 d)
Tue, Aug 20
Wed, Jul 31
Jul 22 2019
Jul 19 2019
Removed some redundancy.
Jul 16 2019
Jul 10 2019
Jul 9 2019
Uploaded the correct patch
Changed predicate for variants with suffixes
Jul 8 2019
Jul 5 2019
Shouldn't the type change be guarded with a conditional compilation construct? I could write
std::list<int> l assert(typeid(void) == typeid(l.unique()));
and expect this assertion to pass when compiling with, say, -std=c++98.
Jul 4 2019
We have a similar problem with our port of libc++ and we also had to conditionalize all uses of long double downstream. Here is a list of files that we had to change: https://pastebin.com/5tTcSYxW
As you see, most of them are tests.
Another problem with long double is that it is used in a couple of places not strictly requiring it (include/locale, include/__mutex_base and include/thread), in those cases we introduced a _LIBCPP_LONGEST_DOUBLE macro which is defined to either double or long double depending on the availability of the latter.
Jul 1 2019
Fix a comment
Jun 27 2019
Subsumed by: https://reviews.llvm.org/D63838
Jun 26 2019
Added a test which uses <2 x double>. Alignment issue should be fixed separately, IMHO.
Jun 25 2019
Jun 21 2019
Jun 19 2019
We maintain such library for an embedded toolchain. Besides, only C++17 and later versions are based on C11.
Jun 18 2019
__libcpp_condvar_timedwait needs to be implemented in a different TU, so it can't be a template and at the same time it needs some sort of time point. I think timespec was chosen because it is what pthread_cond_timedwait expects. Do you think a specialization of chrono::time_point (like chrono::time_point<chrono::system_clock, chrono::nanoseconds> used by condition_variable::__do_timed_wait) would make more sense here?
Jun 17 2019
Jun 14 2019
Jun 13 2019
- Avoid TableGen logic in instruction operands and constraints
Jun 12 2019
- Fixed naming inconsistencies
- Removed comments about undefined instructions
- Factored out common parts of:
- VMINV and VMAXV
- VMINNMV and VMAXNMV
- VMLADAV and VMLSDAV
- VMLALDAV, VMLSLDAV (includes VRMLSLDAVH) and VRMLALDAVH
- Fixed inputs and constraints of non-accumulating instructions
- Split the assembler test into integer and floating point parts
Jun 11 2019
Fixed the tablegen file and tests according to reviewer's comments. Added missing cases to ARMRegisterBankInfo.cpp