Skip to content
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

Fix warnings when built without CRLE #1

Merged
merged 1 commit into from
Jan 27, 2020

Conversation

rgilton
Copy link
Contributor

@rgilton rgilton commented Jan 27, 2020

When building without CRLE, the functions unpack_usize_init and
unpack_usize are not used, resulting in compiler warnings. This
patch moves those functions into the DETOOLS_CONFIG_COMPRESSION_CRLE
region so that these warnings are not generated when CRLE is
disabled.

When building without CRLE, the functions `unpack_usize_init` and
`unpack_usize` are not used, resulting in compiler warnings.  This
patch moves those functions into the DETOOLS_CONFIG_COMPRESSION_CRLE
region so that these warnings are not generated when CRLE is
disabled.
@codecov
Copy link

codecov bot commented Jan 27, 2020

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is 95.65%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   93.56%   93.56%           
=======================================
  Files           5        5           
  Lines        1865     1865           
=======================================
  Hits         1745     1745           
  Misses        120      120
Impacted Files Coverage Δ
src/c/detools.c 92.63% <95.65%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2b7b98b...0c2d367. Read the comment docs.

@eerimoq eerimoq merged commit e9a7fff into eerimoq:master Jan 27, 2020
@eerimoq
Copy link
Owner

eerimoq commented Jan 27, 2020

Thanks!

@eerimoq
Copy link
Owner

eerimoq commented Jan 27, 2020

Btw, may I ask which compression algorithm you are planning to use?

@rgilton
Copy link
Contributor Author

rgilton commented Jan 28, 2020

Sure -- heatshrink, because it performs quite well on the binaries I've shown it. I'd use lzma if I could find a library that used similarly small amounts of memory.

@eerimoq
Copy link
Owner

eerimoq commented Jan 28, 2020

Ok, I added support for it for exactly that reason. I'm glad you found it useful.

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.

None yet

2 participants