Ginkgo: /build/ginkgo-hpc/src/build/include/ginkgo/config.hpp Source File

| Ginkgo Generated from branch based on main. Ginkgo version 1.11.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 11
11#define GKO_VERSION_PATCH 0
12#define GKO_VERSION_TAG "main"
13#define GKO_VERSION_STR 1, 11, 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/* Is std::size_t the same type as std::uint64_t? */
41#define GKO_SIZE_T_IS_UINT64_T
42
43
44/* Should we use all optimizations for Jacobi? */
45/* #undef GINKGO_JACOBI_FULL_OPTIMIZATIONS */
46
47
48/* Should we compile Ginkgo specifically to tune values? */
49/* #undef GINKGO_BENCHMARK_ENABLE_TUNING */
50
51
52/* Should we compile mixed-precision kernels for Ginkgo? */
53/* #undef GINKGO_MIXED_PRECISION */
54
55
56/* What is HIP compiled for, hcc or nvcc? */
57// clang-format off
58#define GINKGO_HIP_PLATFORM_HCC 0
59
60
61#define GINKGO_HIP_PLATFORM_NVCC 0
62// clang-format on
63
64
65/* What is the major version of dpcpp compiler */
66// clang-format off
67#define GINKGO_DPCPP_MAJOR_VERSION 0
68#define GINKGO_DPCPP_MINOR_VERSION 0
69// clang-format on
70
71
72/* Is PAPI SDE available for Logging? */
73// clang-format off
74#define GKO_HAVE_PAPI_SDE 0
75// clang-format on
76
77
78/* Is TAU available for Profiling? */
79// clang-format off
80#define GKO_HAVE_TAU 0
81// clang-format on
82
83
84/* Is VTune ITT available for Profiling? */
85// clang-format off
86#define GKO_HAVE_VTUNE 0
87// clang-format on
88
89
90/* Is METIS available for Reordering? */
91// clang-format off
92#define GKO_HAVE_METIS 0
93// clang-format on
94
95#if GKO_HAVE_METIS
96// clang-format off
97#define GKO_METIS_HEADER <>
98// clang-format on
99#endif
100
101/* Is ROCTX available for Profiling? */
102// clang-format off
103#define GKO_HAVE_ROCTX 0
104// clang-format on
105
106
107/* Is MPI available ? */
108// clang-format off
109#define GINKGO_BUILD_MPI 1
110// clang-format on
111
112/* Is the MPI implementation GPU aware? */
113// clang-format off
114#define GINKGO_HAVE_GPU_AWARE_MPI 0
115// clang-format on
116
117
118/* Is HWLOC available ? */
119// clang-format off
120#define GKO_HAVE_HWLOC 0
121// clang-format on
122
123/* Is half operation available ? */
124// clang-format off
125#define GINKGO_ENABLE_HALF 1
126// clang-format on
127
128/* Is bfloat16 operation available ? */
129// clang-format off
130#define GINKGO_ENABLE_BFLOAT16 1
131// clang-format on
132
133
134/* Do we need to use blocking communication in our SpMV? */
135// clang-format off
136#define GINKGO_HAVE_OPENMPI_PRE_4_1_X 0
137// clang-format on
138
139
140#endif // GKO_INCLUDE_CONFIG_H