Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/isl-0.23/isl_ast_private.h
Examining data/isl-0.23/flow_cmp.c
Examining data/isl-0.23/isl_test_plain_equal_templ.c
Examining data/isl-0.23/isl_schedule_node.c
Examining data/isl-0.23/isl_ctx.c
Examining data/isl-0.23/isl_val.c
Examining data/isl-0.23/isl_map_lexopt_templ.c
Examining data/isl-0.23/isl_multi_align_templ.c
Examining data/isl-0.23/isl_lp_private.h
Examining data/isl-0.23/isl_pw_add_constant_multi_val_templ.c
Examining data/isl-0.23/isl_multi_floor.c
Examining data/isl-0.23/isl_convex_hull.c
Examining data/isl-0.23/isl_union_multi.c
Examining data/isl-0.23/isl_domain_factor_templ.c
Examining data/isl-0.23/isl_pw_insert_dims_templ.c
Examining data/isl-0.23/isl_ast_build.c
Examining data/isl-0.23/isl_box.c
Examining data/isl-0.23/isl_tab.c
Examining data/isl-0.23/isl_multi_gist.c
Examining data/isl-0.23/isl_val_sioimath.c
Examining data/isl-0.23/isl_multi_hash.c
Examining data/isl-0.23/isl_input.c
Examining data/isl-0.23/isl_map_list.c
Examining data/isl-0.23/isl_multi_bind_templ.c
Examining data/isl-0.23/isl_ilp.c
Examining data/isl-0.23/isl_int_sioimath.h
Examining data/isl-0.23/isl_bind_domain_templ.c
Examining data/isl-0.23/test_inputs/codegen/hoist2.c
Examining data/isl-0.23/test_inputs/codegen/roman.c
Examining data/isl-0.23/test_inputs/codegen/separate.c
Examining data/isl-0.23/test_inputs/codegen/isolate7.c
Examining data/isl-0.23/test_inputs/codegen/unroll7.c
Examining data/isl-0.23/test_inputs/codegen/unroll11.c
Examining data/isl-0.23/test_inputs/codegen/redundant.c
Examining data/isl-0.23/test_inputs/codegen/component5.c
Examining data/isl-0.23/test_inputs/codegen/lu.c
Examining data/isl-0.23/test_inputs/codegen/gemm.c
Examining data/isl-0.23/test_inputs/codegen/unroll10.c
Examining data/isl-0.23/test_inputs/codegen/stride6.c
Examining data/isl-0.23/test_inputs/codegen/jacobi_kernel4.c
Examining data/isl-0.23/test_inputs/codegen/disjuncts.c
Examining data/isl-0.23/test_inputs/codegen/separation_class4.c
Examining data/isl-0.23/test_inputs/codegen/sor1d-part.c
Examining data/isl-0.23/test_inputs/codegen/stride5.c
Examining data/isl-0.23/test_inputs/codegen/component3.c
Examining data/isl-0.23/test_inputs/codegen/separation_class.c
Examining data/isl-0.23/test_inputs/codegen/separate2.c
Examining data/isl-0.23/test_inputs/codegen/pldi2012/figure7_b.c
Examining data/isl-0.23/test_inputs/codegen/pldi2012/figure7_d.c
Examining data/isl-0.23/test_inputs/codegen/pldi2012/figure8_a.c
Examining data/isl-0.23/test_inputs/codegen/pldi2012/figure7_c.c
Examining data/isl-0.23/test_inputs/codegen/pldi2012/figure8_b.c
Examining data/isl-0.23/test_inputs/codegen/shift_unroll.c
Examining data/isl-0.23/test_inputs/codegen/separation_class2.c
Examining data/isl-0.23/test_inputs/codegen/isolate5.c
Examining data/isl-0.23/test_inputs/codegen/isolate1.c
Examining data/isl-0.23/test_inputs/codegen/stride7.c
Examining data/isl-0.23/test_inputs/codegen/cholesky.c
Examining data/isl-0.23/test_inputs/codegen/disjuncts2.c
Examining data/isl-0.23/test_inputs/codegen/atomic2.c
Examining data/isl-0.23/test_inputs/codegen/isolate2.c
Examining data/isl-0.23/test_inputs/codegen/shift2.c
Examining data/isl-0.23/test_inputs/codegen/component0.c
Examining data/isl-0.23/test_inputs/codegen/hoist.c
Examining data/isl-0.23/test_inputs/codegen/empty.c
Examining data/isl-0.23/test_inputs/codegen/bilinear.c
Examining data/isl-0.23/test_inputs/codegen/component2.c
Examining data/isl-0.23/test_inputs/codegen/component1.c
Examining data/isl-0.23/test_inputs/codegen/unroll8.c
Examining data/isl-0.23/test_inputs/codegen/single_valued.c
Examining data/isl-0.23/test_inputs/codegen/stride.c
Examining data/isl-0.23/test_inputs/codegen/separation_class3.c
Examining data/isl-0.23/test_inputs/codegen/correlation.c
Examining data/isl-0.23/test_inputs/codegen/omega/fc1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lefur03-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-5.c
Examining data/isl-0.23/test_inputs/codegen/omega/fc2-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride6-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/syr2k-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-5.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak3-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/basics-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/collard-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride6-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m7-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/dagstuhl1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/basics-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu_ijk-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/ge-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/p.delft2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/ts1d-mp-i_ts-m_b-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-6.c
Examining data/isl-0.23/test_inputs/codegen/omega/m9-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter6-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/p6-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/olda-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/fc1-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter3-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-5.c
Examining data/isl-0.23/test_inputs/codegen/omega/dagstuhl1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/m4-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride3-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/p6-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lefur01-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/code_gen-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak3-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/substitution-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/m8-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/substitution-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-5.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride7-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu_ijk-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/m4-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/m1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu_spmd-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/substitution-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/guard1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak4-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride4-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m9-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride5-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m7-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/fc2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m12-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/syr2k-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/p.delft-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/ts1d-orig0-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/code_gen-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/code_gen-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/syr2k-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/m1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m10-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter4-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/guard1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lefur01-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-4.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/substitution-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/chosol-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m3-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m12-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/m11-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/lefur04-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter5-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/hpf-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/olda-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/gist-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/fc1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter1-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift2-5.c
Examining data/isl-0.23/test_inputs/codegen/omega/m10-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/ts1d-check0-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/syr2k-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m2-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride7-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/x-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/stride6-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak2-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter9-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter6-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu_ijk-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/ge-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/if_then-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter8-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/floor_bound-3.c
Examining data/isl-0.23/test_inputs/codegen/omega/m8-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/chosol-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/lu_spmd-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/iter7-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lift1-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/gc-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/wak4-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/x-1.c
Examining data/isl-0.23/test_inputs/codegen/omega/substitution-2.c
Examining data/isl-0.23/test_inputs/codegen/omega/ts1d-check-sblock-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/lefur00-0.c
Examining data/isl-0.23/test_inputs/codegen/omega/m2-1.c
Examining data/isl-0.23/test_inputs/codegen/atomic4.c
Examining data/isl-0.23/test_inputs/codegen/group.c
Examining data/isl-0.23/test_inputs/codegen/component6.c
Examining data/isl-0.23/test_inputs/codegen/unroll9.c
Examining data/isl-0.23/test_inputs/codegen/isolate4.c
Examining data/isl-0.23/test_inputs/codegen/filter.c
Examining data/isl-0.23/test_inputs/codegen/unroll6.c
Examining data/isl-0.23/test_inputs/codegen/dwt.c
Examining data/isl-0.23/test_inputs/codegen/isolate3.c
Examining data/isl-0.23/test_inputs/codegen/shift.c
Examining data/isl-0.23/test_inputs/codegen/unroll4.c
Examining data/isl-0.23/test_inputs/codegen/unroll.c
Examining data/isl-0.23/test_inputs/codegen/isolate6.c
Examining data/isl-0.23/test_inputs/codegen/atomic3.c
Examining data/isl-0.23/test_inputs/codegen/mod.c
Examining data/isl-0.23/test_inputs/codegen/unroll3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-two.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lux.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali6.c
Examining data/isl-0.23/test_inputs/codegen/cloog/usvd_e_t.c
Examining data/isl-0.23/test_inputs/codegen/cloog/wavefront.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-mg-psinv.c
Examining data/isl-0.23/test_inputs/codegen/cloog/min-3-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/guide.c
Examining data/isl-0.23/test_inputs/codegen/cloog/pouchet.c
Examining data/isl-0.23/test_inputs/codegen/cloog/dealII.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mxm-shared.c
Examining data/isl-0.23/test_inputs/codegen/cloog/gesced.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/walters.c
Examining data/isl-0.23/test_inputs/codegen/cloog/0D-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/yosr2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/param-split.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-jacobi3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam6.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-cholesky2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/nul_basic1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/classen2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/nul_basic2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/min-4-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lu.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-fusion1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/otl.c
Examining data/isl-0.23/test_inputs/codegen/cloog/ex1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/classen.c
Examining data/isl-0.23/test_inputs/codegen/cloog/orc.c
Examining data/isl-0.23/test_inputs/codegen/cloog/largeur.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/infinite2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/tiling.c
Examining data/isl-0.23/test_inputs/codegen/cloog/block.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali5.c
Examining data/isl-0.23/test_inputs/codegen/cloog/block2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/multi-mm-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-mg-resid.c
Examining data/isl-0.23/test_inputs/codegen/cloog/0D-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/jacobi-shared.c
Examining data/isl-0.23/test_inputs/codegen/cloog/merge.c
Examining data/isl-0.23/test_inputs/codegen/cloog/forwardsub-1-1-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mod2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/square+triangle-1-1-2-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mod4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-fusion2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/equality2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/youcef.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/swim.c
Examining data/isl-0.23/test_inputs/codegen/cloog/backtrack.c
Examining data/isl-0.23/test_inputs/codegen/cloog/durbin_e_s.c
Examining data/isl-0.23/test_inputs/codegen/cloog/logo.c
Examining data/isl-0.23/test_inputs/codegen/cloog/block3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/cholesky.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lineality-2-1-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-liu-zhuge1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/vasilache.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lu2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-stride2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/gesced3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/forwardsub-2-1-2-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/test.c
Examining data/isl-0.23/test_inputs/codegen/cloog/stride4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/constant.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-jacobi2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/darte.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-loechner3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/singleton.c
Examining data/isl-0.23/test_inputs/codegen/cloog/thomasset.c
Examining data/isl-0.23/test_inputs/codegen/cloog/esced.c
Examining data/isl-0.23/test_inputs/codegen/cloog/uday_scalars.c
Examining data/isl-0.23/test_inputs/codegen/cloog/byu98-1-2-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/equality.c
Examining data/isl-0.23/test_inputs/codegen/cloog/walters2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-loechner5.c
Examining data/isl-0.23/test_inputs/codegen/cloog/dot.c
Examining data/isl-0.23/test_inputs/codegen/cloog/stride3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/levenshtein-1-2-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/4-param.c
Examining data/isl-0.23/test_inputs/codegen/cloog/0D-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/rectangle.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lex.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam5.c
Examining data/isl-0.23/test_inputs/codegen/cloog/nul_lcpc.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-long.c
Examining data/isl-0.23/test_inputs/codegen/cloog/multi-stride2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/stride.c
Examining data/isl-0.23/test_inputs/codegen/cloog/min-2-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mod3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/iftest.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/emploi.c
Examining data/isl-0.23/test_inputs/codegen/cloog/1point-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/logopar.c
Examining data/isl-0.23/test_inputs/codegen/cloog/iftest2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/no_lindep.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-stride.c
Examining data/isl-0.23/test_inputs/codegen/cloog/vivien2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/min-1-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/walters3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-5.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mode.c
Examining data/isl-0.23/test_inputs/codegen/cloog/yosr.c
Examining data/isl-0.23/test_inputs/codegen/cloog/cholesky2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-tang-xue1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/nul_complex1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/union.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/lineality-1-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/stride2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-lim-lam4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-QR.c
Examining data/isl-0.23/test_inputs/codegen/cloog/1point-1.c
Examining data/isl-0.23/test_inputs/codegen/cloog/dot2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-loechner4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/sor1d.c
Examining data/isl-0.23/test_inputs/codegen/cloog/unroll.c
Examining data/isl-0.23/test_inputs/codegen/cloog/youcefn.c
Examining data/isl-0.23/test_inputs/codegen/cloog/basic-bounds-6.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-mg-interp.c
Examining data/isl-0.23/test_inputs/codegen/cloog/mod.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-mg-interp2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/gesced2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-bastoul3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/gauss.c
Examining data/isl-0.23/test_inputs/codegen/cloog/faber.c
Examining data/isl-0.23/test_inputs/codegen/cloog/constbound.c
Examining data/isl-0.23/test_inputs/codegen/cloog/forwardsub-3-1-2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/unroll2.c
Examining data/isl-0.23/test_inputs/codegen/cloog/christian.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-mg-rprj3.c
Examining data/isl-0.23/test_inputs/codegen/cloog/vivien.c
Examining data/isl-0.23/test_inputs/codegen/cloog/reservoir-pingali4.c
Examining data/isl-0.23/test_inputs/codegen/cloog/multi-stride.c
Examining data/isl-0.23/test_inputs/codegen/cloog/donotsimp.c
Examining data/isl-0.23/test_inputs/codegen/component4.c
Examining data/isl-0.23/test_inputs/codegen/unroll2.c
Examining data/isl-0.23/test_inputs/codegen/atomic.c
Examining data/isl-0.23/test_inputs/codegen/component7.c
Examining data/isl-0.23/isl_farkas.c
Examining data/isl-0.23/isl_type_has_space_templ.c
Examining data/isl-0.23/isl_multi_locals_templ.c
Examining data/isl-0.23/isl_multi_param_templ.c
Examining data/isl-0.23/check_reparse_templ.c
Examining data/isl-0.23/isl_map_bound_templ.c
Examining data/isl-0.23/isl_ilp_opt_val_templ.c
Examining data/isl-0.23/isl_arg.c
Examining data/isl-0.23/isl_local_space_private.h
Examining data/isl-0.23/isl_obj.c
Examining data/isl-0.23/isl_schedule.c
Examining data/isl-0.23/isl_ilp_opt_multi_val_templ.c
Examining data/isl-0.23/isl_multi_read_no_explicit_domain_templ.c
Examining data/isl-0.23/isl_pw_sub_templ.c
Examining data/isl-0.23/imath/imrat.c
Examining data/isl-0.23/imath/gmp_compat.c
Examining data/isl-0.23/imath/gmp_compat.h
Examining data/isl-0.23/imath/imrat.h
Examining data/isl-0.23/imath/imath.c
Examining data/isl-0.23/imath/imath.h
Examining data/isl-0.23/isl_schedule_constraints.c
Examining data/isl-0.23/isl_sample.c
Examining data/isl-0.23/isl_test_imath.c
Examining data/isl-0.23/imath_wrap/imrat.c
Examining data/isl-0.23/imath_wrap/gmp_compat.c
Examining data/isl-0.23/imath_wrap/gmp_compat.h
Examining data/isl-0.23/imath_wrap/wrap.h
Examining data/isl-0.23/imath_wrap/imrat.h
Examining data/isl-0.23/imath_wrap/imath.c
Examining data/isl-0.23/imath_wrap/imath.h
Examining data/isl-0.23/isl_union_locals_templ.c
Examining data/isl-0.23/isl_local_space.c
Examining data/isl-0.23/isl_bernstein.h
Examining data/isl-0.23/isl_pw_morph_templ.c
Examining data/isl-0.23/isl_pw_eval.c
Examining data/isl-0.23/polytope_scan.c
Examining data/isl-0.23/isl_bound.c
Examining data/isl-0.23/isl_aff_private.h
Examining data/isl-0.23/isl_options_private.h
Examining data/isl-0.23/isl_map.c
Examining data/isl-0.23/isl_reordering.c
Examining data/isl-0.23/isl_multi_dims.c
Examining data/isl-0.23/bound.c
Examining data/isl-0.23/isl_ctx_private.h
Examining data/isl-0.23/closure.c
Examining data/isl-0.23/isl_flow.c
Examining data/isl-0.23/isl_multi_macro.h
Examining data/isl-0.23/isl_schedule_private.h
Examining data/isl-0.23/isl_multi_add_constant_templ.c
Examining data/isl-0.23/isl_vec_private.h
Examining data/isl-0.23/isl_set_to_ast_graft_list.c
Examining data/isl-0.23/isl_union_map.c
Examining data/isl-0.23/isl_multi_unbind_params_templ.c
Examining data/isl-0.23/isl_multi_align_union_set.c
Examining data/isl-0.23/bset_to_bmap.c
Examining data/isl-0.23/isl_ast.c
Examining data/isl-0.23/isl_test_cpp-checked-conversion.cc
Examining data/isl-0.23/isl_multi_product_templ.c
Examining data/isl-0.23/isl_map_simplify.c
Examining data/isl-0.23/isl_version.c
Examining data/isl-0.23/isl_val_private.h
Examining data/isl-0.23/isl_union_set_private.h
Examining data/isl-0.23/isl_union_pw_templ.c
Examining data/isl-0.23/extract_key.c
Examining data/isl-0.23/isl_aff_lex_templ.c
Examining data/isl-0.23/isl_pw_macro.h
Examining data/isl-0.23/isl_ilp_private.h
Examining data/isl-0.23/isl_pw_move_dims_templ.c
Examining data/isl-0.23/isl_align_params_templ.c
Examining data/isl-0.23/isl_pw_insert_domain_templ.c
Examining data/isl-0.23/uset_to_umap.c
Examining data/isl-0.23/isl_pw_pullback_templ.c
Examining data/isl-0.23/isl_maybe_map.h
Examining data/isl-0.23/include/isl/stream.h
Examining data/isl-0.23/include/isl/union_map_type.h
Examining data/isl-0.23/include/isl/union_set_type.h
Examining data/isl-0.23/include/isl/map_type.h
Examining data/isl-0.23/include/isl/local_space.h
Examining data/isl-0.23/include/isl/union_map.h
Examining data/isl-0.23/include/isl/map.h
Examining data/isl-0.23/include/isl/maybe_templ.h
Examining data/isl-0.23/include/isl/aff.h
Examining data/isl-0.23/include/isl/ast.h
Examining data/isl-0.23/include/isl/multi.h
Examining data/isl-0.23/include/isl/flow.h
Examining data/isl-0.23/include/isl/set.h
Examining data/isl-0.23/include/isl/printer.h
Examining data/isl-0.23/include/isl/id_to_id.h
Examining data/isl-0.23/include/isl/polynomial.h
Examining data/isl-0.23/include/isl/val_gmp.h
Examining data/isl-0.23/include/isl/space.h
Examining data/isl-0.23/include/isl/schedule_type.h
Examining data/isl-0.23/include/isl/list.h
Examining data/isl-0.23/include/isl/hash.h
Examining data/isl-0.23/include/isl/cpp.h
Examining data/isl-0.23/include/isl/ilp.h
Examining data/isl-0.23/include/isl/id_to_pw_aff.h
Examining data/isl-0.23/include/isl/aff_type.h
Examining data/isl-0.23/include/isl/cpp-checked-conversion.h
Examining data/isl-0.23/include/isl/printer_type.h
Examining data/isl-0.23/include/isl/space_type.h
Examining data/isl-0.23/include/isl/mat.h
Examining data/isl-0.23/include/isl/arg.h
Examining data/isl-0.23/include/isl/options.h
Examining data/isl-0.23/include/isl/map_to_basic_set.h
Examining data/isl-0.23/include/isl/maybe_id.h
Examining data/isl-0.23/include/isl/obj.h
Examining data/isl-0.23/include/isl/hmap.h
Examining data/isl-0.23/include/isl/cpp-checked.h
Examining data/isl-0.23/include/isl/ctx.h
Examining data/isl-0.23/include/isl/fixed_box.h
Examining data/isl-0.23/include/isl/vertices.h
Examining data/isl-0.23/include/isl/id.h
Examining data/isl-0.23/include/isl/stride_info.h
Examining data/isl-0.23/include/isl/maybe_basic_set.h
Examining data/isl-0.23/include/isl/constraint.h
Examining data/isl-0.23/include/isl/maybe.h
Examining data/isl-0.23/include/isl/maybe_pw_aff.h
Examining data/isl-0.23/include/isl/union_set.h
Examining data/isl-0.23/include/isl/val.h
Examining data/isl-0.23/include/isl/maybe_ast_expr.h
Examining data/isl-0.23/include/isl/id_to_ast_expr.h
Examining data/isl-0.23/include/isl/point.h
Examining data/isl-0.23/include/isl/set_type.h
Examining data/isl-0.23/include/isl/lp.h
Examining data/isl-0.23/include/isl/val_type.h
Examining data/isl-0.23/include/isl/schedule_node.h
Examining data/isl-0.23/include/isl/ast_type.h
Examining data/isl-0.23/include/isl/schedule.h
Examining data/isl-0.23/include/isl/version.h
Examining data/isl-0.23/include/isl/vec.h
Examining data/isl-0.23/include/isl/hmap_templ.c
Examining data/isl-0.23/include/isl/ast_build.h
Examining data/isl-0.23/include/isl/id_type.h
Examining data/isl-0.23/include/isl/polynomial_type.h
Examining data/isl-0.23/isl_local.h
Examining data/isl-0.23/isl_list_macro.h
Examining data/isl-0.23/isl_maybe_ast_graft_list.h
Examining data/isl-0.23/isl_id_private.h
Examining data/isl-0.23/isl_seq.h
Examining data/isl-0.23/isl_local.c
Examining data/isl-0.23/isl_factorization.h
Examining data/isl-0.23/isl_type_has_equal_space_templ.c
Examining data/isl-0.23/isl_test_cpp-checked.cc
Examining data/isl-0.23/isl_printer.c
Examining data/isl-0.23/isl_multi_nan_templ.c
Examining data/isl-0.23/isl_output.c
Examining data/isl-0.23/opt_type.h
Examining data/isl-0.23/isl_schedule_constraints.h
Examining data/isl-0.23/isl_vertices_private.h
Examining data/isl-0.23/isl_pw_add_constant_val_templ.c
Examining data/isl-0.23/isl_scan.h
Examining data/isl-0.23/isl_imath.h
Examining data/isl-0.23/isl_union_map_private.h
Examining data/isl-0.23/interface/python.cc
Examining data/isl-0.23/interface/extract_interface.h
Examining data/isl-0.23/interface/generator.h
Examining data/isl-0.23/interface/cpp.h
Examining data/isl-0.23/interface/cpp_conversion.h
Examining data/isl-0.23/interface/generator.cc
Examining data/isl-0.23/interface/cpp.cc
Examining data/isl-0.23/interface/cpp_conversion.cc
Examining data/isl-0.23/interface/extract_interface.cc
Examining data/isl-0.23/interface/python.h
Examining data/isl-0.23/isl_union_macro.h
Examining data/isl-0.23/isl_id_to_ast_expr.c
Examining data/isl-0.23/isl_tab.h
Examining data/isl-0.23/isl_schedule_tree.c
Examining data/isl-0.23/isl_printer_private.h
Examining data/isl-0.23/isl_multi_apply_set.c
Examining data/isl-0.23/isl_multi_no_explicit_domain.c
Examining data/isl-0.23/isl_pw_templ.h
Examining data/isl-0.23/isl_schedule_node_private.h
Examining data/isl-0.23/isl_constraint.c
Examining data/isl-0.23/basis_reduction_tab.c
Examining data/isl-0.23/isl_equalities.h
Examining data/isl-0.23/isl_imath.c
Examining data/isl-0.23/check_type_range_templ.c
Examining data/isl-0.23/isl_test_cpp.cc
Examining data/isl-0.23/isl_transitive_closure.c
Examining data/isl-0.23/isl_align_params_bin_templ.c
Examining data/isl-0.23/isl_deprecated.c
Examining data/isl-0.23/isl_multi_splice_templ.c
Examining data/isl-0.23/isl_stream.c
Examining data/isl-0.23/isl_set_list.c
Examining data/isl-0.23/isl_copy_tuple_id_templ.c
Examining data/isl-0.23/isl_multi_min_max_templ.c
Examining data/isl-0.23/isl_multi_apply_templ.c
Examining data/isl-0.23/mp_get_memory_functions.c
Examining data/isl-0.23/isl_fold.c
Examining data/isl-0.23/isl_ast_graft_private.h
Examining data/isl-0.23/isl_stream_private.h
Examining data/isl-0.23/isl_pw_hash.c
Examining data/isl-0.23/isl_ast_codegen.c
Examining data/isl-0.23/isl_space.c
Examining data/isl-0.23/isl_output_private.h
Examining data/isl-0.23/isl_int_imath.h
Examining data/isl-0.23/dep.c
Examining data/isl-0.23/isl_map_to_basic_set.c
Examining data/isl-0.23/isl_local_private.h
Examining data/isl-0.23/set_list_from_map_list_inl.c
Examining data/isl-0.23/isl_pw_bind_domain_templ.c
Examining data/isl-0.23/isl_list_templ.c
Examining data/isl-0.23/isl_point_private.h
Examining data/isl-0.23/isl_id_to_id.c
Examining data/isl-0.23/isl_union_eval.c
Examining data/isl-0.23/isl_multi_no_domain_templ.c
Examining data/isl-0.23/isl_int_sioimath.c
Examining data/isl-0.23/codegen.c
Examining data/isl-0.23/isl_test_list_templ.c
Examining data/isl-0.23/isl_tarjan.h
Examining data/isl-0.23/isl_yaml.h
Examining data/isl-0.23/isl_id_to_pw_aff.c
Examining data/isl-0.23/isl_morph.c
Examining data/isl-0.23/isl_tarjan.c
Examining data/isl-0.23/isl_union_single.c
Examining data/isl-0.23/isl_ast_build_expr.h
Examining data/isl-0.23/isl_bernstein.c
Examining data/isl-0.23/bset_from_bmap.c
Examining data/isl-0.23/isl_lp.c
Examining data/isl-0.23/print_templ.c
Examining data/isl-0.23/isl_options.c
Examining data/isl-0.23/isl_blk.h
Examining data/isl-0.23/isl_test_cpp-generic.cc
Examining data/isl-0.23/isl_multi_align_set.c
Examining data/isl-0.23/isl_unbind_params_templ.c
Examining data/isl-0.23/isl_reordering.h
Examining data/isl-0.23/isl_multi_explicit_domain.c
Examining data/isl-0.23/isl_vec.c
Examining data/isl-0.23/polyhedron_sample.c
Examining data/isl-0.23/isl_range.h
Examining data/isl-0.23/isl_constraint_private.h
Examining data/isl-0.23/isl_schedule_tree.h
Examining data/isl-0.23/isl_polynomial_private.h
Examining data/isl-0.23/uset_from_umap.c
Examining data/isl-0.23/isl_multi_insert_domain_templ.c
Examining data/isl-0.23/isl_coalesce.c
Examining data/isl-0.23/isl_ast_build_expr.c
Examining data/isl-0.23/isl_union_neg.c
Examining data/isl-0.23/isl_range.c
Examining data/isl-0.23/polyhedron_detect_equalities.c
Examining data/isl-0.23/isl_type_has_equal_space_bin_templ.c
Examining data/isl-0.23/isl_multi_move_dims_templ.c
Examining data/isl-0.23/schedule_cmp.c
Examining data/isl-0.23/isl_map_subtract.c
Examining data/isl-0.23/isl_val_gmp.c
Examining data/isl-0.23/isl_power_templ.c
Examining data/isl-0.23/isl_bound.h
Examining data/isl-0.23/print_templ_yaml.c
Examining data/isl-0.23/isl_insert_domain_templ.c
Examining data/isl-0.23/isl_multi_intersect.c
Examining data/isl-0.23/isl_multi_union_pw_aff_explicit_domain.c
Examining data/isl-0.23/isl_pw_lift_templ.c
Examining data/isl-0.23/isl_sample.h
Examining data/isl-0.23/check_reparse_test_templ.c
Examining data/isl-0.23/isl_list_templ.h
Examining data/isl-0.23/isl_id.c
Examining data/isl-0.23/isl_pw_union_opt.c
Examining data/isl-0.23/isl_multi_coalesce.c
Examining data/isl-0.23/print_yaml_field_templ.c
Examining data/isl-0.23/isl_pw_opt_templ.c
Examining data/isl-0.23/isl_multi_templ.c
Examining data/isl-0.23/isl_test_int.c
Examining data/isl-0.23/isl_sort.h
Examining data/isl-0.23/isl_multi_zero_templ.c
Examining data/isl-0.23/isl_schedule_band.c
Examining data/isl-0.23/isl_multi_templ.h
Examining data/isl-0.23/isl_multi_from_base_templ.c
Examining data/isl-0.23/isl_opt_mpa_templ.c
Examining data/isl-0.23/isl_affine_hull.c
Examining data/isl-0.23/isl_dim_map.c
Examining data/isl-0.23/isl_multi_dim_id_templ.c
Examining data/isl-0.23/isl_hash.c
Examining data/isl-0.23/isl_multi_arith_templ.c
Examining data/isl-0.23/isl_dim_map.h
Examining data/isl-0.23/all.h
Examining data/isl-0.23/isl_multi_pw_aff_explicit_domain.c
Examining data/isl-0.23/isl_factorization.c
Examining data/isl-0.23/isl_type_check_equal_space_templ.c
Examining data/isl-0.23/isl_pw_neg_templ.c
Examining data/isl-0.23/isl_seq.c
Examining data/isl-0.23/pip.c
Examining data/isl-0.23/isl_check_named_params_templ.c
Examining data/isl-0.23/isl_blk.c
Examining data/isl-0.23/basis_reduction_templ.c
Examining data/isl-0.23/isl_tab_lexopt_templ.c
Examining data/isl-0.23/has_single_reference_templ.c
Examining data/isl-0.23/schedule.c
Examining data/isl-0.23/isl_pw_locals_templ.c
Examining data/isl-0.23/isl_space_private.h
Examining data/isl-0.23/isl_multi_tuple_id_templ.c
Examining data/isl-0.23/isl_multi_identity_templ.c
Examining data/isl-0.23/isl_multi_apply_union_set.c
Examining data/isl-0.23/isl_multi_cmp.c
Examining data/isl-0.23/isl_config_post.h
Examining data/isl-0.23/print.c
Examining data/isl-0.23/isl_equalities.c
Examining data/isl-0.23/isl_multi_union_add_templ.c
Examining data/isl-0.23/cat.c
Examining data/isl-0.23/isl_pw_templ.c
Examining data/isl-0.23/isl_schedule_read.c
Examining data/isl-0.23/isl_mat.c
Examining data/isl-0.23/check_single_reference_templ.c
Examining data/isl-0.23/isl_pw_add_constant_templ.c
Examining data/isl-0.23/isl_int.h
Examining data/isl-0.23/isl_scan.c
Examining data/isl-0.23/isl_map_private.h
Examining data/isl-0.23/isl_test.c
Examining data/isl-0.23/isl_stride.c
Examining data/isl-0.23/isl_union_templ.c
Examining data/isl-0.23/isl_union_map_lex_templ.c
Examining data/isl-0.23/isl_val_imath.c
Examining data/isl-0.23/isl_aff.c
Examining data/isl-0.23/set_to_map.c
Examining data/isl-0.23/isl_scheduler.c
Examining data/isl-0.23/isl_morph.h
Examining data/isl-0.23/isl_tab_pip.c
Examining data/isl-0.23/isl_vertices.c
Examining data/isl-0.23/isl_project_out_all_params_templ.c
Examining data/isl-0.23/isl_schedule_band.h
Examining data/isl-0.23/isl_ast_graft.c
Examining data/isl-0.23/isl_multi_bind_domain_templ.c
Examining data/isl-0.23/isl_set_to_ast_graft_list.h
Examining data/isl-0.23/isl_ffs.c
Examining data/isl-0.23/polyhedron_minimize.c
Examining data/isl-0.23/isl_polynomial.c
Examining data/isl-0.23/isl_ast_build_private.h
Examining data/isl-0.23/isl_mat_private.h
Examining data/isl-0.23/read_in_string_templ.c
Examining data/isl-0.23/isl_aff_map.c
Examining data/isl-0.23/isl_int_gmp.h
Examining data/isl-0.23/set_from_map.c
Examining data/isl-0.23/isl_gmp.c
Examining data/isl-0.23/isl_sort.c
Examining data/isl-0.23/flow.c
Examining data/isl-0.23/isl_basis_reduction.h
Examining data/isl-0.23/isl_point.c
Examining data/isl-0.23/isl_multi_domain_templ.c
FINAL RESULTS:
data/isl-0.23/flow.c:23:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/flow.c:32:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = isl_union_access_info_compute_flow(access);
data/isl-0.23/imath/gmp_compat.c:397:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(str, s);
data/isl-0.23/include/isl/flow.h:80:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/include/isl/flow.h:84:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/include/isl/flow.h:88:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/include/isl/flow.h:92:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/include/isl/flow.h:96:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/include/isl/flow.h:99:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_keep isl_union_access_info *access);
data/isl-0.23/include/isl/flow.h:101:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access);
data/isl-0.23/include/isl/flow.h:104:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_keep isl_union_access_info *access);
data/isl-0.23/include/isl/flow.h:109:63: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_printer *p, __isl_keep isl_union_access_info *access);
data/isl-0.23/include/isl/flow.h:111:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_keep isl_union_access_info *access);
data/isl-0.23/include/isl/flow.h:115:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access);
data/isl-0.23/interface/cpp.cc:57:9: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
size = vsnprintf(NULL, 0, format, copy);
data/isl-0.23/interface/cpp.cc:60:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(string_pointer, size + 1, format, arguments);
data/isl-0.23/interface/python.cc:113:2: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
vprintf(format, args);
data/isl-0.23/interface/python.cc:134:2: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, pos);
data/isl-0.23/interface/python.cc:137:2: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, pos);
data/isl-0.23/interface/python.cc:139:2: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, pos);
data/isl-0.23/interface/python.cc:145:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/interface/python.cc:150:4: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, i);
data/isl-0.23/interface/python.cc:310:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, arg - skip);
data/isl-0.23/interface/python.cc:313:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, arg - skip);
data/isl-0.23/interface/python.cc:316:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, arg - skip);
data/isl-0.23/interface/python.cc:319:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, arg - skip);
data/isl-0.23/interface/python.cc:350:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/interface/python.cc:352:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/interface/python.cc:355:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/interface/python.cc:358:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/interface/python.cc:480:3: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
printf(fmt, 0);
data/isl-0.23/isl_config_post.h:31:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf _snprintf
data/isl-0.23/isl_config_post.h:31:18: [4] (format) _snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf _snprintf
data/isl-0.23/isl_farkas.c:98:3: [4] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused).
strcpy(prefix_name + prefix_len, name);
data/isl-0.23/isl_flow.c:1504:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map *access[isl_access_end];
data/isl-0.23/isl_flow.c:1513:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1517:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1521:30: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_free(access->access[i]);
data/isl-0.23/isl_flow.c:1524:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
free(access);
data/isl-0.23/isl_flow.c:1531:74: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_ctx *isl_union_access_info_get_ctx(__isl_keep isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1533:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1535:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_map_get_ctx(access->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:1565:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!info->access[isl_access_sink])
data/isl-0.23/isl_flow.c:1568:40: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
space = isl_union_map_get_space(info->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:1571:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!info->access[i])
data/isl-0.23/isl_flow.c:1572:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
info->access[i] = isl_union_map_copy(empty);
data/isl-0.23/isl_flow.c:1579:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!info->access[i])
data/isl-0.23/isl_flow.c:1594:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/isl_flow.c:1600:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1602:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access->access[isl_access_sink] = sink;
data/isl-0.23/isl_flow.c:1603:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_init(access);
data/isl-0.23/isl_flow.c:1613:55: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
enum isl_access_type type, __isl_take isl_union_map *access)
data/isl-0.23/isl_flow.c:1615:16: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!info || !access)
data/isl-0.23/isl_flow.c:1618:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_free(info->access[type]);
data/isl-0.23/isl_flow.c:1619:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
info->access[type] = access;
data/isl-0.23/isl_flow.c:1619:23: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
info->access[type] = access;
data/isl-0.23/isl_flow.c:1624:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_free(access);
data/isl-0.23/isl_flow.c:1631:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/isl_flow.c:1634:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_set(access, isl_access_must_source,
data/isl-0.23/isl_flow.c:1641:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/isl_flow.c:1644:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_set(access, isl_access_may_source,
data/isl-0.23/isl_flow.c:1663:34: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_map_copy(info->access[type]);
data/isl-0.23/isl_flow.c:1699:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
empty = isl_union_map_is_empty(info->access[isl_access_kill]);
data/isl-0.23/isl_flow.c:1707:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/isl_flow.c:1710:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access || !schedule)
data/isl-0.23/isl_flow.c:1717:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:1719:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:1728:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access,
data/isl-0.23/isl_flow.c:1731:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access || !schedule_map)
data/isl-0.23/isl_flow.c:1738:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:1740:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:1746:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_keep isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1751:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1754:34: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_copy(access->access[isl_access_sink]));
data/isl-0.23/isl_flow.c:1757:33: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_copy(access->access[i]));
data/isl-0.23/isl_flow.c:1812:40: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
empty = isl_union_map_is_empty(info->access[type]);
data/isl-0.23/isl_flow.c:1818:60: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return print_yaml_field_union_map(p, key_str[type], info->access[type]);
data/isl-0.23/isl_flow.c:1825:63: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_printer *p, __isl_keep isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1829:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1834:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
p = print_access_field(p, access, i);
data/isl-0.23/isl_flow.c:1853:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_keep isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1858:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1861:55: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
p = isl_printer_to_str(isl_union_access_info_get_ctx(access));
data/isl-0.23/isl_flow.c:1863:45: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
p = isl_printer_print_union_access_info(p, access);
data/isl-0.23/isl_flow.c:1907:18: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map *access, *schedule_map;
data/isl-0.23/isl_flow.c:1923:48: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
info = isl_union_access_info_set(info, key, access);
data/isl-0.23/isl_flow.c:1972:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/isl_flow.c:1980:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:1988:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:1993:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:1996:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
space = isl_union_map_get_space(access->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:1999:37: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_get_space(access->access[i]));
data/isl-0.23/isl_flow.c:2004:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access->access[i] =
data/isl-0.23/isl_flow.c:2005:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_align_params(access->access[i],
data/isl-0.23/isl_flow.c:2013:38: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2017:16: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access->access[i])
data/isl-0.23/isl_flow.c:2018:38: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2020:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:2047:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:2052:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:2058:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access->access[i] =
data/isl-0.23/isl_flow.c:2060:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access->access[i]);
data/isl-0.23/isl_flow.c:2064:16: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access->access[i])
data/isl-0.23/isl_flow.c:2065:38: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2067:37: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2069:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:2651:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:2653:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:2655:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access->access[isl_access_may_source] =
data/isl-0.23/isl_flow.c:2656:34: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_subtract(access->access[isl_access_may_source],
data/isl-0.23/isl_flow.c:2657:34: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_copy(access->access[isl_access_must_source]));
data/isl-0.23/isl_flow.c:2658:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access->access[isl_access_may_source])
data/isl-0.23/isl_flow.c:2659:37: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2661:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:2684:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:2689:46: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_align_params(access);
data/isl-0.23/isl_flow.c:2690:52: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_introduce_schedule(access);
data/isl-0.23/isl_flow.c:2691:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:2694:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
data.must_source = access->access[isl_access_must_source];
data/isl-0.23/isl_flow.c:2695:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
data.may_source = access->access[isl_access_may_source];
data/isl-0.23/isl_flow.c:2697:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
sink = access->access[isl_access_sink];
data/isl-0.23/isl_flow.c:2705:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2708:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:2721:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map *access;
data/isl-0.23/isl_flow.c:2737:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/isl_flow.c:2763:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
space = isl_map_get_space(data->sink[0].access);
data/isl-0.23/isl_flow.c:2767:37: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_get_space(data->sink[i].access));
data/isl-0.23/isl_flow.c:2770:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_get_space(data->source[i].access));
data/isl-0.23/isl_flow.c:2774:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_align_params(data->sink[i].access,
data/isl-0.23/isl_flow.c:2778:41: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_align_params(data->source[i].access,
data/isl-0.23/isl_flow.c:2796:30: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_free(data->sink[i].access);
data/isl-0.23/isl_flow.c:2801:32: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_free(data->source[i].access);
data/isl-0.23/isl_flow.c:2831:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:2838:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_must_source]);
data/isl-0.23/isl_flow.c:2845:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_may_source]);
data/isl-0.23/isl_flow.c:2864:31: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
struct isl_scheduled_access *access;
data/isl-0.23/isl_flow.c:2920:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:2928:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_must_source]);
data/isl-0.23/isl_flow.c:2936:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
umap = isl_union_map_copy(data->access->access[isl_access_may_source]);
data/isl-0.23/isl_flow.c:3014:30: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_access_info *access, struct isl_scheduled_access *sink,
data/isl-0.23/isl_flow.c:3020:50: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
space = isl_space_range(isl_map_get_space(sink->access));
data/isl-0.23/isl_flow.c:3027:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
source_space = isl_map_get_space(source->access);
data/isl-0.23/isl_flow.c:3037:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_access_info_add_source(access,
data/isl-0.23/isl_flow.c:3038:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_map_copy(source->access), source->must, source->node);
data/isl-0.23/isl_flow.c:3042:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/isl-0.23/isl_flow.c:3045:23: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_access_info_free(access);
data/isl-0.23/isl_flow.c:3071:19: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_access_info *access;
data/isl-0.23/isl_flow.c:3078:52: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_access_info_alloc(isl_map_copy(sink->access), sink->node,
data/isl-0.23/isl_flow.c:3080:6: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/isl-0.23/isl_flow.c:3082:32: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = add_matching_sources(access, sink, data);
data/isl-0.23/isl_flow.c:3084:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = access_info_compute_flow_core(access);
data/isl-0.23/isl_flow.c:3134:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:3136:49: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
struct isl_compute_flow_schedule_data data = { access };
data/isl-0.23/isl_flow.c:3142:38: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ctx = isl_union_access_info_get_ctx(access);
data/isl-0.23/isl_flow.c:3162:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
space = isl_union_map_get_space(access->access[isl_access_sink]);
data/isl-0.23/isl_flow.c:3172:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:3175:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:3201:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
__isl_take isl_union_access_info *access)
data/isl-0.23/isl_flow.c:3207:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
has_kill = isl_union_access_has_kill(access);
data/isl-0.23/isl_flow.c:3211:48: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
must = isl_union_access_info_get_must_source(access);
data/isl-0.23/isl_flow.c:3212:46: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
may = isl_union_access_info_get_may_source(access);
data/isl-0.23/isl_flow.c:3214:57: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_add_kill_to_must_source(access);
data/isl-0.23/isl_flow.c:3215:43: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_normalize(access);
data/isl-0.23/isl_flow.c:3216:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access)
data/isl-0.23/isl_flow.c:3219:32: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = compute_flow_schedule(access);
data/isl-0.23/isl_flow.c:3221:33: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = compute_flow_union_map(access);
data/isl-0.23/isl_flow.c:3226:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info_free(access);
data/isl-0.23/isl_flow.c:3304:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/isl_flow.c:3308:49: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_set_must_source(access, must_source);
data/isl-0.23/isl_flow.c:3309:48: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_set_may_source(access, may_source);
data/isl-0.23/isl_flow.c:3310:50: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_set_schedule_map(access, schedule);
data/isl-0.23/isl_flow.c:3311:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = isl_union_access_info_compute_flow(access);
data/isl-0.23/isl_int_sioimath.c:206:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(out, "%*" PRIi32, width, small);
data/isl-0.23/isl_int_sioimath.h:541:3: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(result, 12, "%" PRIi32, isl_sioimath_get_small(val));
data/isl-0.23/isl_tab.c:4199:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(out, (i == tab->n_param ||
data/isl-0.23/isl_test.c:59:2: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf(filename, pattern, srcdir, name, suffix);
data/isl-0.23/isl_test.c:3595:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map *access, *schedule;
data/isl-0.23/isl_test.c:3606:33: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
r = isl_union_map_compute_flow(access, isl_union_map_copy(access),
data/isl-0.23/isl_test.c:3606:60: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
r = isl_union_map_compute_flow(access, isl_union_map_copy(access),
data/isl-0.23/isl_test.c:3607:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_map_copy(access), schedule,
data/isl-0.23/isl_test.c:4634:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
isl_union_access_info *access;
data/isl-0.23/isl_test.c:4680:49: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_set_must_source(access, source);
data/isl-0.23/isl_test.c:4681:46: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access = isl_union_access_info_set_schedule(access, schedule);
data/isl-0.23/isl_test.c:4682:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
flow = isl_union_access_info_compute_flow(access);
data/isl-0.23/include/isl/cpp-checked.h:3439:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:3577:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:3825:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:3869:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:3913:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:3988:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4021:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4054:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4087:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4120:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4153:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4186:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4219:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4252:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4285:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4318:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4351:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4384:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4417:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4450:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4483:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4516:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4549:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4582:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4615:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4648:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4681:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4714:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4747:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4780:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4813:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4846:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4939:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:4983:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5077:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5149:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5287:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5342:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5386:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5577:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5762:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5866:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:5949:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:6097:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:6636:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:6952:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:7097:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:7479:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:7737:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:7969:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:8045:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:8387:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:8525:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:8852:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:8990:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9095:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9285:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9681:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9852:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9896:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9940:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:9995:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10039:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10083:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10127:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10160:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10193:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10226:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10259:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10749:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:10897:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:11004:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:11135:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:11718:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:11907:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:12045:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:12301:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:12617:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:12755:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:13192:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/include/isl/cpp-checked.h:13340:8: [3] (random) setstate:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
os.setstate(std::ios_base::badbit);
data/isl-0.23/flow_cmp.c:40:9: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file = fopen(filename, "r");
data/isl-0.23/imath/imath.c:121:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(q__, p__, i__); \
data/isl-0.23/imath/imath.c:1995:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(new, old, osize * sizeof(mp_digit));
data/isl-0.23/isl_arg.c:216:8: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
const char *prefix[10];
data/isl-0.23/isl_arg.c:538:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char val[20];
data/isl-0.23/isl_arg.c:1027:8: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
*p = atoi(val);
data/isl-0.23/isl_ast.c:1673:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char *op_str[isl_ast_expr_op_last + 1];
data/isl-0.23/isl_ast.c:2704:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char printed[isl_ast_expr_op_last + 1];
data/isl-0.23/isl_ast_build.c:103:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[23];
data/isl-0.23/isl_farkas.c:97:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(prefix_name, prefix, prefix_len);
data/isl-0.23/isl_gmp.c:16:34: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char *data = (unsigned char *)v[0]._mp_d;
data/isl-0.23/isl_id.c:238:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[50];
data/isl-0.23/isl_output.c:45:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_to[2] = { " -> ", " \\to " };
data/isl-0.23/isl_output.c:46:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_and[2] = { " and ", " \\wedge " };
data/isl-0.23/isl_output.c:47:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_or[2] = { " or ", " \\vee " };
data/isl-0.23/isl_output.c:48:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_le[2] = { "<=", "\\le" };
data/isl-0.23/isl_output.c:49:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_ge[2] = { ">=", "\\ge" };
data/isl-0.23/isl_output.c:50:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_open_set[2] = { "{ ", "\\{\\, " };
data/isl-0.23/isl_output.c:51:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_close_set[2] = { " }", " \\,\\}" };
data/isl-0.23/isl_output.c:52:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_open_list[2] = { "[", "(" };
data/isl-0.23/isl_output.c:53:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_close_list[2] = { "]", ")" };
data/isl-0.23/isl_output.c:54:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_such_that[2] = { " : ", " \\mid " };
data/isl-0.23/isl_output.c:55:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_open_exists[2] = { "exists (", "\\exists \\, " };
data/isl-0.23/isl_output.c:56:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_close_exists[2] = { ")", "" };
data/isl-0.23/isl_output.c:57:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_div_prefix[2] = { "e", "\\alpha_" };
data/isl-0.23/isl_output.c:58:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_mod[2] = { "mod", "\\bmod" };
data/isl-0.23/isl_output.c:59:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_param_prefix[2] = { "p", "p_" };
data/isl-0.23/isl_output.c:60:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_input_prefix[2] = { "i", "i_" };
data/isl-0.23/isl_output.c:61:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const char *s_output_prefix[2] = { "o", "o_" };
data/isl-0.23/isl_output.c:211:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[20];
data/isl-0.23/isl_printer.c:77:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(p->buf + p->buf_n, s, len);
data/isl-0.23/isl_scheduler.c:6206:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[40];
data/isl-0.23/isl_sort.c:102:17: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (b, ls, lo - ls);
data/isl-0.23/isl_sort.c:107:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (b, hs, hi - hs);
data/isl-0.23/isl_sort.c:111:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (b, ls, lo - ls);
data/isl-0.23/isl_sort.c:116:13: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (a1, buf, copied);
data/isl-0.23/isl_sort.c:125:9: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (b, lo, am - lo);
data/isl-0.23/isl_sort.c:129:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy (a1, buf, copied);
data/isl-0.23/isl_test.c:481:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
input = fopen(filename, "r");
data/isl-0.23/isl_test.c:1226:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
input = fopen(filename, "r");
data/isl-0.23/isl_test.c:1261:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
input = fopen(filename, "r");
data/isl-0.23/isl_test.c:1585:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
input = fopen(filename, "r");
data/isl-0.23/isl_test.c:1694:10: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
input = fopen(filename, "r");
data/isl-0.23/isl_test.c:7879:8: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
const char *vertex[6];
data/isl-0.23/isl_test.c:9657:18: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
valid = name && atoi(name + 1) == data->depth;
data/isl-0.23/pip.c:344:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char s[1024];
data/isl-0.23/schedule_cmp.c:39:9: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file = fopen(filename, "r");
data/isl-0.23/check_reparse_templ.c:15:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/check_reparse_templ.c:24:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/check_reparse_templ.c:26:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/flow_cmp.c:89:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/flow_cmp.c:115:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/flow_cmp.c:117:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/imath/gmp_compat.c:396:16: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
str = malloc(strlen(s)+1);
data/isl-0.23/imath/imath.c:1783:25: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (!s_pad(z, s_inlen(strlen(str), radix)))
data/isl-0.23/imath/imrat.c:508:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(str);
data/isl-0.23/imath/imrat.c:616:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(start);
data/isl-0.23/include/isl/hmap_templ.c:281:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/include/isl/hmap_templ.c:284:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/include/isl/hmap_templ.c:286:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/interface/generator.cc:854:27: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return base.substr(strlen(get_prefix));
data/isl-0.23/interface/generator.h:18:28: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return strncmp(s, prefix, strlen(prefix));
data/isl-0.23/interface/generator.h:112:33: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return method_name(fd).substr(strlen(set_callback_prefix));
data/isl-0.23/isl_aff.c:700:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:709:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:709:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:710:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:2994:49: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
__isl_take isl_pw_aff *pwaff2, int strict, int equal)
data/isl-0.23/isl_aff.c:3014:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_aff.c:3335:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:3353:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:3355:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_aff.c:4308:68: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
__isl_take isl_multi_aff *ma1, __isl_take isl_multi_aff *ma2, int equal)
data/isl-0.23/isl_aff.c:4317:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_aff.c:4351:68: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
__isl_take isl_multi_aff *ma1, __isl_take isl_multi_aff *ma2, int equal)
data/isl-0.23/isl_aff.c:4366:49: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return isl_multi_aff_lex_gte_set_0d(ma1, ma2, equal);
data/isl-0.23/isl_aff.c:4387:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_aff.c:5927:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:5935:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:5937:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_aff.c:5946:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || src_n_div < 0 || dst_n_div < 0)
data/isl-0.23/isl_aff.c:5948:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_aff.c:6862:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:6870:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_aff.c:6870:19: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_aff.c:6871:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6884:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6897:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal, equal_params;
data/isl-0.23/isl_aff.c:6919:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6923:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:6923:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:6924:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6928:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:6928:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_aff.c:6929:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6947:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:6955:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_aff.c:6955:19: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_aff.c:6956:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:6969:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_aff.c:8631:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:8646:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:8648:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_aff.c:9313:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:9326:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:9328:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_aff.c:9371:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:9389:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:9391:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_aff.c:9445:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:9462:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:9464:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_aff.c:9527:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_aff.c:9543:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_aff.c:9545:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_arg.c:234:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
prefixes->len[prefixes->n] = strlen(prefix);
data/isl-0.23/isl_arg.c:260:10: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len += strlen(prefixes->prefix[i]) + 1;
data/isl-0.23/isl_arg.c:316:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len += strlen(decl->long_name);
data/isl-0.23/isl_arg.c:326:10: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len += strlen(decl->long_name);
data/isl-0.23/isl_arg.c:351:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(s);
data/isl-0.23/isl_arg.c:385:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(default_prefix) + strlen(def) + strlen(default_suffix);
data/isl-0.23/isl_arg.c:385:33: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(default_prefix) + strlen(def) + strlen(default_suffix);
data/isl-0.23/isl_arg.c:385:47: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(default_prefix) + strlen(def) + strlen(default_suffix);
data/isl-0.23/isl_arg.c:433:10: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
pos += strlen(decl->u.choice.choice[i].name);
data/isl-0.23/isl_arg.c:447:12: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int len = strlen(default_prefix) + strlen(default_suffix);
data/isl-0.23/isl_arg.c:447:37: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int len = strlen(default_prefix) + strlen(default_suffix);
data/isl-0.23/isl_arg.c:454:11: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len += strlen(decl->u.flags.flags[i].name);
data/isl-0.23/isl_arg.c:504:11: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
pos += strlen(decl->u.flags.flags[j].name);
data/isl-0.23/isl_arg.c:531:19: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return pos + 3 + strlen(name);
data/isl-0.23/isl_arg.c:748:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (end - start == strlen(decl->long_name) &&
data/isl-0.23/isl_arg.c:768:14: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
const char *equal;
data/isl-0.23/isl_arg.c:787:24: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (need_argument && !equal)
data/isl-0.23/isl_arg.c:791:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
*has_argument = !!equal;
data/isl-0.23/isl_arg.c:792:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
end = equal ? equal : name + strlen(name);
data/isl-0.23/isl_arg.c:792:16: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
end = equal ? equal : name + strlen(name);
data/isl-0.23/isl_arg.c:792:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
end = equal ? equal : name + strlen(name);
data/isl-0.23/isl_arg.c:799:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal ? equal + 1 : end;
data/isl-0.23/isl_arg.c:887:35: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (!set_flag(decl, &val, flags, strlen(flags)))
data/isl-0.23/isl_arg.c:938:41: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (match_long_name(decl, name, name + strlen(name))) {
data/isl-0.23/isl_ast.c:400:13: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_ast.c:403:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_ast.c:403:22: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_ast.c:404:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_ast_codegen.c:3288:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_ast_codegen.c:3312:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_ast_graft.c:148:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_ast_graft.c:148:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_ast_graft.c:154:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_ast_graft.c:212:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_ast_graft.c:228:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_ast_graft.c:231:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal || n == 1) {
data/isl-0.23/isl_ast_graft.c:238:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_coalesce.c:2921:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_coalesce.c:2942:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_coalesce.c:2944:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
else if (equal)
data/isl-0.23/isl_coalesce.c:3494:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal, empty;
data/isl-0.23/isl_coalesce.c:3512:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal || empty < 0 || empty) {
data/isl-0.23/isl_coalesce.c:3512:19: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal || empty < 0 || empty) {
data/isl-0.23/isl_coalesce.c:3514:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || empty < 0)
data/isl-0.23/isl_coalesce.c:3885:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal, empty;
data/isl-0.23/isl_coalesce.c:3908:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || empty < 0)
data/isl-0.23/isl_coalesce.c:3910:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal || empty) {
data/isl-0.23/isl_constraint.c:308:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_constraint.c:315:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_constraint.c:315:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_constraint.c:316:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_farkas.c:75:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size_t prefix_len = strlen(prefix);
data/isl-0.23/isl_farkas.c:94:25: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
prefix_len + strlen(name) + 1);
data/isl-0.23/isl_farkas.c:159:22: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
size_t prefix_len = strlen(prefix);
data/isl-0.23/isl_flow.c:928:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_map *equal;
data/isl-0.23/isl_flow.c:943:30: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
map = isl_map_range_product(equal, isl_map_copy(old_map));
data/isl-0.23/isl_fold.c:487:13: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int sgn, equal;
data/isl-0.23/isl_fold.c:490:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_fold.c:492:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_hash.c:169:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_hash.c:174:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_hash.c:176:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_input.c:120:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(s);
data/isl-0.23/isl_int_gmp.h:86:17: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
(*mp_free)(s, strlen(s) + 1); \
data/isl-0.23/isl_int_sioimath.c:174:6: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
if (strlen(str) < 10) {
data/isl-0.23/isl_local_space.c:190:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_local_space.c:193:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_local_space.c:193:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_local_space.c:194:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_local_space.c:808:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_local_space.c:838:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_local_space.c:840:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_lp.c:326:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_lp.c:333:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_lp.c:335:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_map.c:3770:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:3799:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:3801:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_map.c:4664:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:4667:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:4669:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_map.c:5234:18: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
unsigned n, int equal)
data/isl-0.23/isl_map.c:5239:16: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (n == 0 && equal)
data/isl-0.23/isl_map.c:5248:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_map.c:5260:73: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
static __isl_give isl_map *map_lex_lte(__isl_take isl_space *space, int equal)
data/isl-0.23/isl_map.c:5264:48: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return map_lex_lte_first(space, space->n_out, equal);
data/isl-0.23/isl_map.c:5290:18: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
unsigned n, int equal)
data/isl-0.23/isl_map.c:5295:16: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (n == 0 && equal)
data/isl-0.23/isl_map.c:5304:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_map.c:5316:73: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
static __isl_give isl_map *map_lex_gte(__isl_take isl_space *space, int equal)
data/isl-0.23/isl_map.c:5320:48: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return map_lex_gte_first(space, space->n_out, equal);
data/isl-0.23/isl_map.c:5721:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:5726:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_map.c:5726:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_map.c:5728:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:5730:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_map.c:5804:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:5809:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_map.c:5809:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_map.c:5811:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:5813:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_map.c:8155:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_map.c:8161:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:8163:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_map.c:8324:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:8329:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:8331:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal) {
data/isl-0.23/isl_map.c:8531:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:8534:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:8536:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_map.c:8629:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:8632:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:8634:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_map.c:9105:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:9108:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_map.c:9108:19: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_map.c:9109:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_map.c:10388:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:10396:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:10396:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:10397:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_map.c:10406:14: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
for (i = 0; equal && i < map1->n; ++i) {
data/isl-0.23/isl_map.c:10408:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map.c:10413:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_map.c:11889:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal, is_identity;
data/isl-0.23/isl_map.c:11892:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:11892:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:11893:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_map.c:14270:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_map.c:14282:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:14282:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_map.c:14283:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_map.c:14286:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_map.c:14286:19: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_map.c:14287:23: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return isl_bool_not(equal);
data/isl-0.23/isl_map_simplify.c:3672:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_map_simplify.c:3690:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map_simplify.c:3692:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_map_simplify.c:4848:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_map_simplify.c:4890:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal ? lower : bmap->n_ineq;
data/isl-0.23/isl_map_subtract.c:537:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal, disjoint;
data/isl-0.23/isl_map_subtract.c:546:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_map_subtract.c:548:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_multi_add_constant_templ.c:56:17: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool zero, equal;
data/isl-0.23/isl_multi_add_constant_templ.c:66:27: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (zero < 0 || n < 0 || equal < 0)
data/isl-0.23/isl_multi_add_constant_templ.c:68:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_multi_explicit_domain.c:167:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_multi_explicit_domain.c:178:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_multi_explicit_domain.c:190:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_multi_explicit_domain.c:199:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_multi_explicit_domain.c:201:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_multi_templ.c:873:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_multi_templ.c:880:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:880:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:881:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_multi_templ.c:885:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:885:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:886:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_multi_templ.c:892:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:892:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_multi_templ.c:893:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_polynomial.c:1442:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_polynomial.c:1461:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_polynomial.c:2190:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_polynomial.c:2199:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_polynomial.c:2199:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_polynomial.c:2200:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_polynomial.c:2203:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_polynomial.c:2203:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_polynomial.c:2204:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_printer.c:106:38: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
p = str_print(p, p->indent_prefix, strlen(p->indent_prefix));
data/isl-0.23/isl_printer.c:109:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
p = str_print(p, p->prefix, strlen(p->prefix));
data/isl-0.23/isl_printer.c:116:31: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
p = str_print(p, p->suffix, strlen(p->suffix));
data/isl-0.23/isl_printer.c:117:25: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
p = str_print(p, "\n", strlen("\n"));
data/isl-0.23/isl_printer.c:131:25: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
return str_print(p, s, strlen(s));
data/isl-0.23/isl_printer.c:176:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
len = strlen(s);
data/isl-0.23/isl_pw_templ.c:943:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_pw_templ.c:946:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_pw_templ.c:948:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_pw_templ.c:960:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_pw_templ.c:962:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_pw_templ.c:964:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_pw_templ.c:2016:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal, has_nan;
data/isl-0.23/isl_pw_templ.c:2030:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_pw_templ.c:2030:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_pw_templ.c:2031:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_pw_templ.c:2041:14: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
for (i = 0; equal && i < pw1->n; ++i) {
data/isl-0.23/isl_pw_templ.c:2043:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_pw_templ.c:2045:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_pw_templ.c:2048:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_pw_templ.c:2054:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_schedule_band.c:186:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_schedule_band.c:202:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_band.c:202:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_band.c:203:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_schedule_node.c:1803:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_schedule_node.c:1811:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_schedule_node.c:1813:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_schedule_node.c:1918:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_schedule_node.c:1926:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_schedule_node.c:1928:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_schedule_tree.c:631:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_schedule_tree.c:656:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_schedule_tree.c:656:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_schedule_tree.c:683:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_tree.c:683:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_tree.c:684:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_schedule_tree.c:701:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_tree.c:701:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_schedule_tree.c:702:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_space.c:1055:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:1064:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:1064:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:1065:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_space.c:1091:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:1094:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:1094:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:1095:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_space.c:1432:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:1435:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_space.c:1437:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_space.c:1874:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:1880:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_space.c:1882:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_space.c:1934:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:1942:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_space.c:1948:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_space.c:2421:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_space.c:2428:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:2428:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || !equal)
data/isl-0.23/isl_space.c:2429:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_stream.c:233:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c = fgetc(s->file);
data/isl-0.23/isl_tab_pip.c:468:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_tab_pip.c:478:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_test.c:52:11: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
length = strlen(pattern) - 6 + strlen(srcdir) + strlen(name)
data/isl-0.23/isl_test.c:52:33: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
length = strlen(pattern) - 6 + strlen(srcdir) + strlen(name)
data/isl-0.23/isl_test.c:52:50: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
length = strlen(pattern) - 6 + strlen(srcdir) + strlen(name)
data/isl-0.23/isl_test.c:53:5: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
+ strlen(suffix) + 1;
data/isl-0.23/isl_test.c:76:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:84:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:86:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:477:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:495:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:497:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:577:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:594:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:596:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:618:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:630:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:630:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:636:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:638:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:651:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:653:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1301:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:1311:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:1313:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1426:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:1438:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:1440:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1466:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:1478:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:1480:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1656:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:1665:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:1667:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1791:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:1803:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:1805:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:1947:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:1969:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal_input < 0 || equal_intersection < 0)
data/isl-0.23/isl_test.c:1971:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:2048:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:2059:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:2061:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:2652:18: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool exact, equal;
data/isl-0.23/isl_test.c:2775:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:2779:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:2998:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:3042:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3044:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3067:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3069:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3308:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:3317:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_test.c:3322:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:3325:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3327:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3338:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3347:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_test.c:3354:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3357:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3359:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3370:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3379:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_test.c:3387:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3390:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3392:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3718:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3732:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3734:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3771:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:3830:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3832:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3844:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3846:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3880:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:3893:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3895:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3911:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3913:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:3929:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:3941:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:3943:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:4214:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:4230:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:4232:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:4248:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:4250:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:4567:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:4576:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:4578:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:6795:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_stat equal;
data/isl-0.23/isl_test.c:6802:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:6835:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_stat equal;
data/isl-0.23/isl_test.c:6902:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7571:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:7592:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7594:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7606:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7608:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7620:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7622:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7642:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:7642:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:7649:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7651:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7667:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7669:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7683:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7685:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:7697:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_stat equal;
data/isl-0.23/isl_test.c:7710:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7781:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:7799:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:7808:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7810:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_test.c:7814:37: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int expected = pma_equal_tests[i].equal;
data/isl-0.23/isl_test.c:7822:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7824:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal != expected)
data/isl-0.23/isl_test.c:7907:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:7921:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_test.c:7921:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal)
data/isl-0.23/isl_test.c:7928:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:7931:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal ? isl_stat_ok : isl_stat_error;
data/isl-0.23/isl_test.c:7995:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:8005:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8007:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8090:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:8102:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8104:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8156:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8170:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8172:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8594:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:8604:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8606:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8619:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:8633:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8635:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8647:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:8661:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8663:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8676:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8699:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8701:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8760:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8768:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8778:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8785:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8793:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8801:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8809:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8817:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8825:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8835:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8842:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8854:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8861:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8900:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8917:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8919:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8974:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:8986:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:8988:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:8999:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9001:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9012:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9014:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9073:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:9084:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9086:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9112:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9123:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9125:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9152:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9162:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9164:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9192:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9205:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9207:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9239:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9252:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9254:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9283:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9292:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9294:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_test.c:9337:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9347:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9349:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9396:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9409:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9411:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9459:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9469:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9471:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9486:10: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int ok, equal;
data/isl-0.23/isl_test.c:9501:16: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (ok < 0 || equal < 0)
data/isl-0.23/isl_test.c:9503:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:9983:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:9996:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:9998:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10014:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:10038:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10040:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10060:44: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool involves1, involves2, involves3, equal;
data/isl-0.23/isl_test.c:10078:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10078:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10083:57: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (involves1 < 0 || involves2 < 0 || involves3 < 0 || equal < 0)
data/isl-0.23/isl_test.c:10085:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10139:12: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:10153:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10155:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10326:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test.c:10355:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10357:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10369:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:10402:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10402:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10404:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10404:20: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10414:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10416:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10434:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal, equal_expansion;
data/isl-0.23/isl_test.c:10509:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0 || equal_expansion < 0)
data/isl-0.23/isl_test.c:10511:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10576:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:10585:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10587:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10593:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:10602:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10604:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test.c:10662:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
int equal;
data/isl-0.23/isl_test.c:10697:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10697:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && equal)
data/isl-0.23/isl_test.c:10705:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test.c:10707:8: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test_list_templ.c:21:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test_list_templ.c:43:15: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (n < 0 || equal < 0)
data/isl-0.23/isl_test_list_templ.c:46:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_test_plain_equal_templ.c:23:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test_plain_equal_templ.c:33:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
return equal;
data/isl-0.23/isl_test_plain_equal_templ.c:41:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_test_plain_equal_templ.c:44:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_test_plain_equal_templ.c:46:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_type_check_equal_space_templ.c:15:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_type_check_equal_space_templ.c:18:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_type_check_equal_space_templ.c:20:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
data/isl-0.23/isl_union_map.c:2983:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_union_map.c:2986:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && !equal)
data/isl-0.23/isl_union_map.c:2986:21: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal >= 0 && !equal)
data/isl-0.23/isl_union_map.c:2989:32: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
*non_identity = isl_bool_not(equal);
data/isl-0.23/isl_union_map.c:4124:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_union_map.c:4129:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_union_map.c:4131:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal) {
data/isl-0.23/isl_union_multi.c:350:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_union_multi.c:354:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_union_multi.c:356:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/isl_union_single.c:98:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/isl_union_single.c:115:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/isl_union_single.c:117:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal)
data/isl-0.23/read_in_string_templ.c:17:28: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
static __isl_give TYPE *FN(read,BASE)(__isl_keep isl_stream *s)
data/isl-0.23/schedule_cmp.c:57:11: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
isl_bool equal;
data/isl-0.23/schedule_cmp.c:73:6: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (equal < 0)
data/isl-0.23/schedule_cmp.c:75:7: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
if (!equal)
ANALYSIS SUMMARY:
Hits = 875
Lines analyzed = 229521 in approximately 5.64 seconds (40690 lines/second)
Physical Source Lines of Code (SLOC) = 166391
Hits@level = [0] 332 [1] 563 [2] 47 [3] 81 [4] 184 [5] 0
Hits@level+ = [0+] 1207 [1+] 875 [2+] 312 [3+] 265 [4+] 184 [5+] 0
Hits/KSLOC@level+ = [0+] 7.254 [1+] 5.2587 [2+] 1.8751 [3+] 1.59263 [4+] 1.10583 [5+] 0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.