| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
those we need to by-pass realloc routines and fall-back to allocate as new - copy - delete. The remaining problem is that we don't have any mechanism to accurately determine whether a type is relocatable or not, so currently let's be super conservative using either RequireInitialization or std::is_trivially_copyable
|
| |
|
|
|
|
|
|
|
| |
EIGEN_DECLARE_TEST(mytest) { /* code */ }.
This provide several advantages:
- more flexibility in designing unit tests
- unit tests can be glued to speed up compilation
- unit tests are compiled with same predefined macros, which is a requirement for zapcc
|
| |
|
|
| |
(used to work in 3.2.9 though the expression is not really writable)
|
| | |
|
| | |
|
| | |
|
| |
|
Gael Guennebaud
Christoph Hertzberg