forked from starpu-runtime/starpu
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.dev
125 lines (89 loc) · 3.21 KB
/
README.dev
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
# StarPU --- Runtime system for heterogeneous multicore architectures.
#
# Copyright (C) 2009-2021 Université de Bordeaux, CNRS (LaBRI UMR 5800), Inria
#
# StarPU is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or (at
# your option) any later version.
#
# StarPU is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
# See the GNU Lesser General Public License in COPYING.LGPL for more details.
#
Contents
========
- Directory structure
- Developer Warnings
- Naming Conventions
- Coding Style
- Error handling
Directory structure
-------------------
The directory structure is as follows:
- src : internal source for StarPU
- include : public API
- tests : unitary tests
- examples : examples using StarPU
- doc : documentation for StarPU
- tools : tools for StarPU
StarPU extensions have their own directory (src/include/tests/examples) structure:
- mpi : The MPI support
- socl : the StarPU OpenCL-compatible interface
- sc_hypervisor : The Scheduling Context Hypervisor
- starpufft : The FFT support
- eclipse-plugin : The Eclipse Plugin
- starpupy : The StarPU Python Interface
- starpurm : The StarPU Resource Manager
Some directories contain only build system details:
- build-aux
- m4
- autom4te.cache
Developer Warnings
------------------
They are enabled only if the STARPU_DEVEL environment variable is
defined to a non-empty value, when calling configure.
Naming Conventions
------------------
* Prefix names of public objects (types, functions, etc.) with "starpu"
* Prefix names of internal objects (types, functions, etc.) with "_starpu"
* Names for qualified types (struct, union, enum) do not end with _t, _s or similar.
Use _t only for typedef types, such as opaque public types, e.g
typedef struct _starpu_data_state* starpu_data_handle_t;
or
typedef uint64_t starpu_tag_t;
* When a variable can only take a finite set of values, use an enum
type instead of defining macros for each of the values.
Coding Style
------------
* Curly braces always go on a new line
Error handling
--------------
* Use STARPU_ABORT() for catastrophic errors, from which StarPU will never
recover.
switch (node_kind)
{
case STARPU_CPU_RAM:
do_stg();
break;
...
default:
/* We cannot be here */
STARPU_ABORT();
}
* Use STARPU_ASSERT() to run checks that are very likely to succeed, but still
are useful for debugging purposes. It should be OK to disable them with
--enable-fast.
STARPU_ASSERT(j->terminated != 0)
Makefile.am
-----------
Dependency libraries are appended to LIBS.
Only real LDFLAGS such as -no-undefined go to LDFLAGS.
If a program foo needs more libraries, it can put then in foo_LDADD.
(No, AM_LDADD does not exist)
All install rules must use $(DESTDIR) so that
./configure --prefix=/usr && make && make install DESTDIR=/tmp/foobar
can properly work, as it is used by distributions. That can easily checked by
*not* running it as root.