Issue616

Title Update Boost headers
Priority feature Status resolved
Superseder Nosy List florian, jendrik, malte
Assigned To jendrik Keywords
Optional summary

Created on 2016-01-05.15:58:27 by jendrik, last changed by florian.

Messages
msg5047 (view) Author: florian Date: 2016-01-07.19:44:57
We removed the boost headers in issue617.
msg5031 (view) Author: malte Date: 2016-01-05.18:54:37
Sounds good! If it helps, I also volunteer to contribute to replacements for
boost::any and/or boost::dynamic_bitset. Sounds like a fun self-contained
programming task. :-)

But I'm not sure how soon I could do this, so feel free to ignore this or come
back to the offer at a later time.
msg5030 (view) Author: florian Date: 2016-01-05.18:51:34
We discussed this and came up with the following suggestion.

Jendrik will try to avoid the boost dependency in issue600 and I will try to
remove the dependency on boost::any in issue617.

If we both succeed, we can close this issue as obsolete.

If Jendrik succeeds and I can't find a good alternative for "any", we could
still update the existing files of boost to a more up-to-date version, which
would avoid annoying warnings on Windows.

If it turns out that we need boost's bitset for efficient CEGAR code, we'll
discuss our options again.
msg5027 (view) Author: malte Date: 2016-01-05.18:19:27
Better, but I'd still be somewhat reluctant to pay that price if it's only a
temporary addition anyway and we're planning to remove the dynamic_bitset code
from ext soon anyway.
msg5026 (view) Author: florian Date: 2016-01-05.18:12:05
We could also use boost-1.54 (the boost version of Ubuntu 14.04) which "only"
adds 2.5 MB.
msg5024 (view) Author: malte Date: 2016-01-05.17:36:02
If we ever get around to creating the slimmer repository we were planning to
create, perhaps it would be a bad idea to add the rather large dynamic_bitset
headers. Once added, they remain in the history forever unless we strip the
history again, and I think we shouldn't plan to add things that we would later
strip.

Some size considerations. Currently, I get the following sizes for the working
directory of a fresh clone:

331.7 MB benchmarks
  6.0 MB src
  1.9 MB experiments
  0.4 MB misc
  0.1 MB driver

We can split up the src directory further:
  3.5 MB search
  1.8 MB VAL
  0.6 MB translate
  0.1 MB preprocess
 <0.1 MB cmake_modules

And splitting up src/search further:
  1.4 MB ext
  2.1 MB (everything else)

If we remove the benchmarks and VAL, we end up with working directory size of
6.6 MB. If we additionally remove ext, we end up with a size of 5.2 MB.

If we add the new boost code to this, we have 16.2 MB, i.e., the size triples
because of boost. This is perhaps a bit much.
msg5018 (view) Author: jendrik Date: 2016-01-05.15:58:27
Remove all current Boost files then add all Boost version 1.60 headers required 
by any.hpp or dynamic_bitset.hpp.
History
Date User Action Args
2016-01-07 19:44:57floriansetstatus: chatting -> resolved
messages: + msg5047
summary: On hold until there is some progress in issue600 and issue617. ->
2016-01-05 18:54:37maltesetmessages: + msg5031
2016-01-05 18:51:34floriansetmessages: + msg5030
summary: On hold until there is some progress in issue600 and issue617.
2016-01-05 18:19:27maltesetmessages: + msg5027
2016-01-05 18:12:05floriansetmessages: + msg5026
2016-01-05 17:36:02maltesetstatus: unread -> chatting
messages: + msg5024
2016-01-05 15:58:27jendrikcreate