From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <rguenther@suse.de>
Cc: kugan <kugan.vivekanandarajah@linaro.org>,
Jan Hubicka <hubicka@ucw.cz>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC][IPA-VRP] ADDR_EXPR and nonnull
Date: Wed, 19 Oct 2016 14:26:00 -0000 [thread overview]
Message-ID: <20161019142620.GA69032@kam.mff.cuni.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1610191125150.2258@t29.fhfr.qr>
> > Would excluding weak symbols (I believe I can check DECL_WEAK for this) good
> > enough. Or looking for acceptable subset would work?
>
> I think we should add a symtab helper to tell if address_nonzero_p (if
> that doesn't aleady exist).
We have node->nonzero_address()
Honza
>
> Richard.
>
> > Thanks,
> > Kugan
> >
> > >
> > > Richard.
> > >
> > > > Attached patch bootstraps and regression testing didn't introduce any new
> > > > regressions.
> > > >
> > > > Thanks,
> > > > Kugan
> > > >
> > > >
> > > > gcc/ChangeLog:
> > > >
> > > > 2016-10-19 Kugan Vivekanandarajah <kuganv@linaro.org>
> > > >
> > > > * ipa-prop.c (ipa_compute_jump_functions_for_edge): Set
> > > > value range to nonull for ADDR_EXPR.
> > > >
> > > > gcc/testsuite/ChangeLog:
> > > >
> > > > 2016-10-19 Kugan Vivekanandarajah <kuganv@linaro.org>
> > > >
> > > > * gcc.dg/ipa/vrp5.c: New test.
> > > > * gcc.dg/ipa/vrp6.c: New test.
> > > >
> > >
> >
> >
>
> --
> Richard Biener <rguenther@suse.de>
> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
next prev parent reply other threads:[~2016-10-19 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 2:12 kugan
2016-10-19 8:24 ` Richard Biener
2016-10-19 8:48 ` kugan
2016-10-19 9:26 ` Richard Biener
2016-10-19 14:26 ` Jan Hubicka [this message]
2016-10-20 3:13 ` kugan
2016-10-20 7:42 ` Richard Biener
2016-10-20 11:56 ` kugan
2016-10-20 12:09 ` Richard Biener
2016-10-20 12:15 ` Jan Hubicka
2016-10-21 3:39 ` kugan
2016-10-21 7:16 ` Richard Biener
2016-10-21 7:38 ` kugan
2016-10-21 8:08 ` 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=20161019142620.GA69032@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.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).