From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][1/2] Fix PR77768
Date: Thu, 29 Sep 2016 07:12:00 -0000 [thread overview]
Message-ID: <20160929050648.GA9969@x4> (raw)
In-Reply-To: <alpine.LSU.2.11.1609281328320.26629@t29.fhfr.qr>
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
next prev parent reply other threads:[~2016-09-29 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 11:37 Richard Biener
2016-09-29 7:12 ` Markus Trippelsdorf [this message]
2016-09-29 7:36 ` Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160929050648.GA9969@x4 \
--to=markus@trippelsdorf.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).