This solves a problem that is introduced by unconditionally setting
`HAVE_VC=1` in config.h:

If a compilation unit is compiled without the `-fabi-version=6` or similar
then the compilers vector types (which are used by Vc under the hood if
available) will mangle to the same string, irrespective of the number of lanes
they actually use.  This makes certain overloaded function definitions in the
Vc headers clash, since their only difference is whether they apply to
e.g. AVX types (4 lanes) or SSE types (2 lanes).

This is normally not a problem, since any program that uses Vc needs to have a
call to `add_dune_vc_flags()` in `CMakeLists.txt`.  However, since I now want
to put support for vectorized types into the `fmatrix.hh`, any compilation
unit that uses a `FieldMatrix` will automatically include the Vc headers
because `config.h` unconditionally sets `HAVE_VC=1`.

Using the HAVE/ENABLE-trick makes sure that the value of `HAVE_VC` is in sync
with the compilation flags.

Note: I tried using `COMPILE_DEFINITION` for `ENABLE_VC=1` in
      `dune_register_package_flags()`, but that will always add
      `-DENABLE_VC=1` to the compiler command line, even when
      `add_dune_vc_flags()` hasn't been called for that target, and
      `dune_enable_all_packages()` isn't in use.  Using `COMPILE_OPTIONS`
      instead seems inappropriate, but does work.

When you can't avoid operating on the individual lanes of a simd vector.

add_dune_test: Handle complex expressions in `CMAKE_GUARD`

The check `if(NOT ${condition})` does not behave as expected when
`condition` is a complex string expression such as `A OR B`. It does
however work when `condition` is a list.

Therefore convert `condition` to a list by calling `separate_arguments`.

Note that this change also adds missing parenthesis around `condition`
which also results in wrong results for complex expressions.

Closes issue #39.

See merge request !117

The check `if(NOT ${condition})` does not behave as expected when
`condition` is a complex string expression such as `A OR B`. It does
however work when `condition` is a list.

Therefore convert `condition` to a list by calling `separate_arguments`.

Note that this change also adds missing parenthesis around `condition`
which also results in wrong results for complex expressions.

Closes issue #39.

Move documentation for MPI_RANKS to the right place

The paragraph describing the `MPI_RANKS` parameter was under the
description of the `CMAKE_GUARD` parameter.

See merge request !116

The paragraph describing the `MPI_RANKS` parameter was under the
description of the `CMAKE_GUARD` parameter.

Feature/improved cmake test skipping

#28 did not get much attention by fellow developers, so I hope this implementation
will draw some attention...

This MR adds a CMAKE_GUARD option to dune_add_test

A list of conditions can be passed to the argument. CMake
will evaluate these conditions, and if one of them does not
evaluate to TRUE, the test sources will be replaced by a dummy
source, that returns 77.

This option should be used instead of guarding the call to
dune_add_test with a cmake if-clause. The idea behind it is
to always give the user an idea of which tests are available,
but have not been run on his system.


Furthermore, the MR makes SKIP_ON_77 enabled by default, no need
to specify it manually anymore.


See merge request !100

[cmake] fix installation of communication.pdf

Closes #36

See merge request !115

This function is needed since we cannot add a dependency to the install
target.
Since we only need this function for generated PDFs, I removed the part
that searches for the PDF in the source dir.

Closes #36

This reverts commit 68d7266b.

[CMake] Remove all pre-CMake 2.8.12 compatibility code



See merge request !108

Feature/update uselatex.cmake to 2.3.0

@robert.kloefkorn I added an auto-detection of in-source builds which disables LaTeX. You might want to give it a try. If it works, we can also back-port the very commit to 2.4.2.

See merge request !109

* Use FORCE_DVI instead of DEFAULT_SAFEPDF
* FATHER doc and DEFAULT_PDF not needed
* old arguments are filtered/translated and a
  deprecation warning is emitted

Christoph Grüninger authored 9 years ago and Christoph Grüninger committed 8 years ago

No longer needed, as tarballs will never contain generated
files. Thes files can now be simply installed without any
magic.

Christoph Grüninger authored 9 years ago and Christoph Grüninger committed 8 years ago

* Add some line breaks to indicate structure
* Use lower-case function names
* Use TRUE and FALSE instead of ON and empty variable values

Christoph Grüninger authored 9 years ago and Christoph Grüninger committed 8 years ago

* Fix whitespace

add support for vectorization library Vc

This branch adds support for the Vc library, which add support for vectorization, including an abstraction for intrisics.

We have been using in EXA-Dune and I belive that the integration of vectorization support into the core-Dune is something Dune in general can benefit from. A separate branch I'm preparing for ISTL will add support for multiple RHS vectors using vectorization.

The branch collects a set of helper classes which allow to add vectorization support to your code with moderate effort. Mainly this means that we have a couple of utility functions, which work for scalar data types, ranges and SIMD data types alike.

See also: !16, core/dune-istl!17, core/dune-geometry!13.

**Note**: This is the followup merge request to !16.  The original was merged accidentially and had to be reverted, see #26.  The branch had to be rebased; if you had checked out an earlier version of feature/vc you may need to take special action to rebase onto the new branch.#


See merge request !81

This avoids unnecessary build system inspection.

[doc] minor corrections



See merge request !114