Archived issue #0024635

Eliminate trivial compiler warnings by GCC in Debug mode

Open CASCADEOCCT:Codingclosed4 public notes

Search issues

Description

GCC produces many more warnings in Debug mode than in optimized, due to inconsistent use of #ifdef DEB statement such that some good fragments of code become disabled in Debug mode, and some unused variables become defined.

Public activity

4 archived notes

Participants are labeled by their role within this record.

01Commenter 1
Fix pushed to CR24635, please review (note that in BRepFill classes some messages to cout previously output when DEB is defined now will be output only when DRAW is defined)
02Commenter 2
Ok.
03Commenter 3
Release mode.

Dear BugMaster,

Branch CR24635 (and products from GIT master) was compiled on Linux and Windows platforms and tested.
[revision removed]

Number of compiler warnings:

occt component :
Linux: 29 (29 on master)
Windows: 0 (0 on master)

products component :
Linux: 12 (12 on master)
Windows: 2 (2 on master)

Regressions/Differences:
No regressions/differences

Testing cases:
Not needed

Testing on Linux:
Total MEMORY difference: 382753204 / 383419896
Total CPU difference: 42055.19999999991 / 42572.35999999976

Testing on Windows:
Total MEMORY difference: 428996736 / 429063576
Total CPU difference: 31825.59375 / 33299.265625

There are not differences in images found by testdiff.
04Commenter 4
Debug mode.

Dear BugMaster,

Branch CR24635 (and products from GIT master) was compiled on Linux and Windows platforms and tested on DEBUG mode.

Number of compiler warnings:

occt component :
Linux: 15 (66 on master)
Windows: 0 (0 on master)

products component :
Linux: 7 (7 on master)
Windows: 0 (10 on master)

Regressions/Differences:
No regressions/differences