Rafael Sá Menezes

Update: after new version of Z3. The program is solved faster: 3s. Boolector stil takes a fraction of a second. Now the main issue is the CE generation. We take...

> Is this with a release build? No, debug. > We could try perf record and perf report I will take a shot at it later.

I think that could work, my main remakes would be: 1. Where is the best place for the transformation? I fear that we may get slowdowns if we do it...

> Wrt. #1585 I think we need a way to opt-in for --32 and --64 tests, for big and little endian ones, basically everything that changes the default architecture settings....

> First, I'd suggest to keep space as separator for readibility. Then to make the format something like this: > ``` > ... > ... > ... > > ......

We can could also use [Labels](https://cmake.org/cmake/help/latest/prop_test/LABELS.html#prop_test:LABELS) from ctest. I guess we could use both the mode and directory as labels for now. What I am unsure is how to comunicate...

Not sure which groups that we should create. It might be worth to check what are the flags that we actually use in our tests: ``` '16', '32', '64', 'add-symex-value-set',...

Closing since #881 supersedes this.

> How about we use a global variable? > > From the documentation, we are not allowed to free the get_env return > string anyway. > > Em qui., 3...

> > That could work for `get_env` but the main use case is for users having to initialize structs and buffers in their harness. > > I see. > >...