Ginkgo Generated from branch based on main. Ginkgo version 1.9.0
A numerical linear algebra library targeting many-core architectures
 
Loading...
Searching...
No Matches
config.hpp
1// SPDX-FileCopyrightText: 2017 - 2024 The Ginkgo authors
2//
3// SPDX-License-Identifier: BSD-3-Clause
4
5#ifndef GKO_INCLUDE_CONFIG_H
6#define GKO_INCLUDE_CONFIG_H
7
8// clang-format off
9#define GKO_VERSION_MAJOR 1
10#define GKO_VERSION_MINOR 9
11#define GKO_VERSION_PATCH 0
12#define GKO_VERSION_TAG "main"
13#define GKO_VERSION_STR 1, 9, 0
14// clang-format on
15
16
17// clang-format off
18#define GINKGO_VERSION_TAG_DEPRECATED 0
19#if GINKGO_VERSION_TAG_DEPRECATED
20#pragma message ("The branch " GKO_VERSION_TAG " is deprecated and will stop receiving updates after 2025. " \
21 "Please use the main branch for the latest release, or the develop branch for the latest development updates.")
22#endif
23// clang-format on
24
25
26/*
27 * Controls the amount of messages output by Ginkgo.
28 * 0 disables all output (except for test, benchmarks and examples).
29 * 1 activates important messages.
30 */
31// clang-format off
32#define GKO_VERBOSE_LEVEL 1
33// clang-format on
34
35
36/* Is Itanium ABI available? */
37#define GKO_HAVE_CXXABI_H
38
39
40/* Should we use all optimizations for Jacobi? */
41/* #undef GINKGO_JACOBI_FULL_OPTIMIZATIONS */
42
43
44/* Should we compile Ginkgo specifically to tune values? */
45/* #undef GINKGO_BENCHMARK_ENABLE_TUNING */
46
47
48/* Should we compile mixed-precision kernels for Ginkgo? */
49/* #undef GINKGO_MIXED_PRECISION */
50
51
52/* What is HIP compiled for, hcc or nvcc? */
53// clang-format off
54#define GINKGO_HIP_PLATFORM_HCC 0
55
56
57#define GINKGO_HIP_PLATFORM_NVCC 0
58// clang-format on
59
60
61/* What is the major version of dpcpp compiler */
62// clang-format off
63#define GINKGO_DPCPP_MAJOR_VERSION 0
64#define GINKGO_DPCPP_MINOR_VERSION 0
65// clang-format on
66
67
68/* Is PAPI SDE available for Logging? */
69// clang-format off
70#define GKO_HAVE_PAPI_SDE 0
71// clang-format on
72
73
74/* Is TAU available for Profiling? */
75// clang-format off
76#define GKO_HAVE_TAU 0
77// clang-format on
78
79
80/* Is VTune ITT available for Profiling? */
81// clang-format off
82#define GKO_HAVE_VTUNE 0
83// clang-format on
84
85
86/* Is METIS available for Reordering? */
87// clang-format off
88#define GKO_HAVE_METIS 0
89// clang-format on
90
91#if GKO_HAVE_METIS
92// clang-format off
93#define GKO_METIS_HEADER <>
94// clang-format on
95#endif
96
97/* Is ROCTX available for Profiling? */
98// clang-format off
99#define GKO_HAVE_ROCTX 0
100// clang-format on
101
102
103/* Is MPI available ? */
104// clang-format off
105#define GINKGO_BUILD_MPI 1
106// clang-format on
107
108/* Is the MPI implementation GPU aware? */
109// clang-format off
110#define GINKGO_HAVE_GPU_AWARE_MPI 0
111// clang-format on
112
113
114/* Is HWLOC available ? */
115// clang-format off
116#define GKO_HAVE_HWLOC 0
117// clang-format on
118
119/* Is half operation available ? */
120// clang-format off
121#define GINKGO_ENABLE_HALF 1
122// clang-format on
123
124
125/* Do we need to use blocking communication in our SpMV? */
126// clang-format off
127/* #undef GINKGO_FORCE_SPMV_BLOCKING_COMM */
128// clang-format on
129
130
131#endif // GKO_INCLUDE_CONFIG_H