Skip to content

Allow characters with value >= 128 in XML output #7109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 8, 2022

Conversation

thomasspriggs
Copy link
Contributor

These values are used as part of printable characters which should be allowed in XML output. This invariant was previously violated for characters such as ¬ and which are included in the output when cbmc is invoked with --verbosity 10 --xml-ui. This was due to the comparison formerly being a signed comparison. So byte values in the range 128 to 255 were treated as values in the -128 to -1 range which are less than which has value 32.

This PR should address issue #7038

  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

These values are used as part of printable characters which should be
allowed in XML output. This invariant was previously violated for
characters such as `¬` and `⇔` which are included in the output when
cbmc is invoked with `--verbosity 10 --xml-ui`. This was due to the
comparison formerly being a signed comparison. So byte values in the
range 128 to 255 were treated as values in the -128 to -1 range which
are less than ` ` which has value 32.
@codecov
Copy link

codecov bot commented Sep 7, 2022

Codecov Report

Merging #7109 (8691d65) into develop (e6fc280) will increase coverage by 0.04%.
The diff coverage is 94.91%.

@@             Coverage Diff             @@
##           develop    #7109      +/-   ##
===========================================
+ Coverage    77.87%   77.92%   +0.04%     
===========================================
  Files         1576     1576              
  Lines       181587   181611      +24     
===========================================
+ Hits        141412   141512     +100     
+ Misses       40175    40099      -76     
Impacted Files Coverage Δ
src/cpp/cpp_template_type.h 52.94% <0.00%> (-11.35%) ⬇️
src/goto-instrument/dump_c.cpp 80.86% <0.00%> (ø)
src/goto-instrument/function.cpp 0.00% <0.00%> (ø)
src/util/xml.cpp 73.88% <ø> (ø)
src/ansi-c/c_typecheck_type.cpp 77.16% <86.66%> (+0.05%) ⬆️
.../src/java_bytecode/java_bytecode_convert_class.cpp 94.18% <100.00%> (+0.01%) ⬆️
...src/java_bytecode/java_bytecode_typecheck_type.cpp 96.00% <100.00%> (ø)
jbmc/src/java_bytecode/java_object_factory.cpp 94.40% <100.00%> (+0.02%) ⬆️
jbmc/src/java_bytecode/java_pointer_casts.cpp 92.50% <100.00%> (ø)
jbmc/src/java_bytecode/java_types.cpp 95.13% <100.00%> (+0.02%) ⬆️
... and 29 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@thomasspriggs thomasspriggs merged commit 6259f6c into diffblue:develop Sep 8, 2022
@thomasspriggs thomasspriggs deleted the tas/xml_invariant branch September 8, 2022 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants