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 | /*******************************************************************************
* Copyright 2016-2018 Intel Corporation
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*******************************************************************************/
#ifndef CPU_REF_POOLING_HPP
#define CPU_REF_POOLING_HPP
#include <assert.h>
#include "c_types_map.hpp"
#include "type_helpers.hpp"
#include "utils.hpp"
#include "cpu_pooling_pd.hpp"
#include "cpu_primitive.hpp"
namespace mkldnn {
namespace impl {
namespace cpu {
template <impl::data_type_t data_type, impl::data_type_t acc_type = data_type>
struct ref_pooling_fwd_t: public cpu_primitive_t {
struct pd_t: public cpu_pooling_fwd_pd_t {
using cpu_pooling_fwd_pd_t::cpu_pooling_fwd_pd_t;
DECLARE_COMMON_PD_T("ref:any", ref_pooling_fwd_t);
status_t init() {
bool ok = true
&& set_default_params() == status::success
&& is_fwd()
&& utils::everyone_is(data_type, src_md()->data_type,
dst_md()->data_type)
&& desc()->accum_data_type == acc_type
&& attr()->has_default_values();
if (!ok) return status::unimplemented;
bool is_training = desc_.prop_kind == prop_kind::forward_training;
if (desc()->alg_kind == alg_kind::pooling_max && is_training)
init_default_ws();
return status::success;
}
};
ref_pooling_fwd_t(const pd_t *apd): cpu_primitive_t(apd) {}<--- Struct 'ref_pooling_fwd_t < data_type :: f32 , data_type :: f32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_fwd_t < data_type :: f32 , data_type :: f32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided. <--- Struct 'ref_pooling_fwd_t < data_type :: s32 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_fwd_t < data_type :: s32 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided. <--- Struct 'ref_pooling_fwd_t < data_type :: s8 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_fwd_t < data_type :: s8 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided. <--- Struct 'ref_pooling_fwd_t < data_type :: u8 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_fwd_t < data_type :: u8 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
typedef typename prec_traits<data_type>::type data_t;
typedef typename prec_traits<acc_type>::type acc_data_t;
virtual status_t execute(const exec_ctx_t &ctx) const override {
execute_forward(ctx);
return status::success;
}
private:
void execute_forward(const exec_ctx_t &ctx) const;
const pd_t *pd() const { return (const pd_t *)primitive_t::pd(); }<--- C-style pointer casting [+]C-style pointer casting detected. C++ offers four different kinds of casts as replacements: static_cast, const_cast, dynamic_cast and reinterpret_cast. A C-style cast could evaluate to any of those automatically, thus it is considered safer if the programmer explicitly states which kind of cast is expected. See also: https://www.securecoding.cert.org/confluence/display/cplusplus/EXP05-CPP.+Do+not+use+C-style+casts.
};
template <impl::data_type_t data_type, impl::data_type_t acc_type = data_type>
struct ref_pooling_bwd_t: public cpu_primitive_t {
struct pd_t: public cpu_pooling_bwd_pd_t {
using cpu_pooling_bwd_pd_t::cpu_pooling_bwd_pd_t;
DECLARE_COMMON_PD_T("ref:any", ref_pooling_bwd_t);
status_t init() {
bool ok = true
&& set_default_params() == status::success
&& !is_fwd()
&& utils::everyone_is(data_type, diff_dst_md()->data_type,
diff_src_md()->data_type)
&& attr()->has_default_values();
if (!ok) return status::unimplemented;
if (desc()->alg_kind == alg_kind::pooling_max) {
init_default_ws();
if (!compare_ws(hint_fwd_pd_))
return status::unimplemented;
}
return status::success;
}
};
ref_pooling_bwd_t(const pd_t *apd): cpu_primitive_t(apd) {}<--- Struct 'ref_pooling_bwd_t < data_type :: f32 , data_type :: f32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_bwd_t < data_type :: f32 , data_type :: f32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided. <--- Struct 'ref_pooling_bwd_t < data_type :: s32 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. [+]Struct 'ref_pooling_bwd_t < data_type :: s32 , data_type :: s32 >' has a constructor with 1 argument that is not explicit. Such constructors should in general be explicit for type safety reasons. Using the explicit keyword in the constructor means some mistakes when using the class can be avoided.
typedef typename prec_traits<data_type>::type data_t;
typedef typename prec_traits<acc_type>::type acc_data_t;
virtual status_t execute(const exec_ctx_t &ctx) const override {
execute_backward(ctx);
return status::success;
}
private:
void execute_backward(const exec_ctx_t &ctx) const;
const pd_t *pd() const { return (const pd_t *)primitive_t::pd(); }<--- C-style pointer casting [+]C-style pointer casting detected. C++ offers four different kinds of casts as replacements: static_cast, const_cast, dynamic_cast and reinterpret_cast. A C-style cast could evaluate to any of those automatically, thus it is considered safer if the programmer explicitly states which kind of cast is expected. See also: https://www.securecoding.cert.org/confluence/display/cplusplus/EXP05-CPP.+Do+not+use+C-style+casts.
};
}
}
}
#endif
// vim: et ts=4 sw=4 cindent cino^=l0,\:0,N-s
|