Cleanup some python warnings. No functional change.

This commit is contained in:
Wilson Snyder 2021-03-20 17:37:24 -04:00
parent b6c393e9f0
commit 93eabb83b2
5 changed files with 7 additions and 5 deletions

1
.gitignore vendored
View File

@ -36,5 +36,6 @@ verilator_coverage_bin*
verilator.pc
verilator-config.cmake
verilator-config-version.cmake
**/__pycache__/*
**/_build/*
**/obj_dir/*

View File

@ -508,8 +508,8 @@ PYLINT = pylint
PYLINT_FLAGS = --disable=R0801
lint-py:
$(FLAKE8) $(FLAKE8_FLAGS) $(PY_PROGRAMS)
$(PYLINT) $(PYLINT_FLAGS) $(PY_PROGRAMS)
-$(FLAKE8) $(FLAKE8_FLAGS) $(PY_PROGRAMS)
-$(PYLINT) $(PYLINT_FLAGS) $(PY_PROGRAMS)
format-pl-exec:
-chmod a+x test_regress/t/*.pl

View File

@ -362,7 +362,7 @@ Some relevant files and directories in this package are as follows:
::
Changes => Version history
README.rst => This document
README.rst => This document
bin/verilator => Compiler wrapper invoked to Verilate code
docs/ => Additional documentation
examples/make_hello_c => Example GNU-make simple Verilog->C++ conversion

View File

@ -47,7 +47,7 @@ def test():
# to uncovered (in G++ 9.3.0) even with all inlining turned off.
# Having false negative coverage is more effort then missing negatives.
# Also this seems to explode the runtime (since a lot more data).
#+ " -fkeep-inline-functions"
# + " -fkeep-inline-functions"
# Otherwise static may not show as uncovered
+ " -fkeep-static-functions"
# Exceptions can pollute the branch coverage data

View File

@ -602,7 +602,8 @@ def write_type_enum(fh, typen, idx, processed, kind, indent):
def write_types(filename):
with open_file(filename) as fh:
fh.write(" enum en : uint16_t {\n")
(final, last) = write_type_enum(fh, "Node", 0, {}, "concrete-enum", 2)
(final, ignored) = write_type_enum( # pylint: disable=W0612
fh, "Node", 0, {}, "concrete-enum", 2)
fh.write(" _ENUM_END = " + str(final) + "\n")
fh.write(" };\n")