On 2016.09.28 at 13:33 +0200, Richard Biener wrote: > > I am testing the following patch to avoid useless VRP range allocations > when we just ask for varying on stmts we don't know how to handle. > I think it should fix the PR where we end up assigning to the > static const vr_const_varying returned by get_value_range in the early VRP > context. > > Eventually the VRP lattice needs to become sparse (or just growable, I > have a patch for that as well). Not until early VRP gets some more > capabilities though, it would be a waste otherwise. > > Bootstrap / regtest in progress on x86_64-unknown-linux-gnu.
You probably noticed this yourself, but the patch causes conftests to spin during stageprofile. For example libiberty: configure:6516: checking for working fork configure:6538: /home/trippels/gcc_build_dir_/./prev-gcc/xgcc -B/home/trippels/gcc_build_dir_/./prev-gcc/ -B/usr/local/powerpc64le-unknown-linux-gnu/bin/ -B/usr/local/powerpc64le-unknown-linux-gnu/bin/ -B/usr/local/powerpc64le-unknown-linux-gnu/lib/ -isystem /usr/local/powerpc64le-unknown-linux-gnu/include -isystem /usr/local/powerpc64le-unknown-linux-gnu/sys-include -o conftest -mcpu=power8 -O3 -pipe -gtoggle -fprofile-generate -static-libstdc++ -static-libgcc conftest.c >&5 configure:6538: $? = 0 configure:6538: ./conftest <<spinning>> -- Markus