Vladimír Štill

@dbeyer, would it please be possible to clarify this officially? I can see @danieldietsch's point, but it would be good to have it specified on the SV-COMP website.

@PhilippWendler, well, 30 GB (and 58 TB in case of `init-4-n-u_true-unreach-call`) does not seem very reasonable even for heap allocation to me. I can see that motivation for these benchmarks...

I implemented your comments. As far as the whole-worker or just-build problem goes, my original intention was to prevent users with low priority from using system resources though Nix, but...

Hi, what is the status of this? The last comment is more than a year old and I am wondering if cgroups v2 will work soon as they have important...

As far as I know, Archlinux and Fedora 31+ already use v2 hierarchy by default (actually it should be default since Systemd v248). So its importance will increase. As for...

@PhilippWendler, if you suggest using other distribution as a solution, that is not acceptable in many cases. For example, we cannot have dedicated machines for SV-COMP – we need to...

Thank you. OK, just to be safe, the size of `some_type_t stack[N]` is `N * sizeof(some_type_t)` if and only if `some_type_t` is sized?

Thanks, but I am actually concerned with the size in the `p4c` compiler which (`Type::width_bits()`) is currently returning zero in this case.