From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <rguenther@suse.de>
Cc: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
Jan Hubicka <hubicka@ucw.cz>, Martin Jambor <mjambor@suse.cz>,
Kugan Vivekanandarajah <kugan.vivekanandarajah@linaro.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] ipa bitwise constant propagation
Date: Thu, 04 Aug 2016 13:05:00 -0000 [thread overview]
Message-ID: <20160804130549.GA77269@kam.mff.cuni.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1608040928260.30444@t29.fhfr.qr>
> I didn't look at the propagation part but eventually the IPA-CP
> lattice gets quite big. Also the alignment lattice is very
> similar to the bits lattice so why not merge those two? But
This was always the original idea to replace alignment propagation by bitwise
ccp. I suppose we only have issue here because nonzero bits are not tracked for
pointers so we need to feed the original lattices by hand?
We could also make use of VR ranges and bits while evaultaing predicates
in ipa-inline-analysis. I can look into it after returning from Leeds.
Honza
> in the end it's Martins/Honzas call here. Note there is
> trailing_wide_ints <> which could be used to improve memory usage
> based on the underlying type.
>
> Thanks,
> Richard.
next prev parent reply other threads:[~2016-08-04 13:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 6:36 Prathamesh Kulkarni
2016-08-04 8:02 ` Richard Biener
2016-08-04 8:57 ` Prathamesh Kulkarni
2016-08-04 9:07 ` kugan
2016-08-04 10:51 ` Richard Biener
2016-08-04 13:05 ` Jan Hubicka [this message]
2016-08-04 23:04 ` kugan
2016-08-05 11:36 ` Jan Hubicka
2016-08-05 12:37 ` Martin Jambor
2016-08-07 21:38 ` Prathamesh Kulkarni
2016-08-08 14:04 ` Martin Jambor
2016-08-08 14:29 ` David Malcolm
2016-08-09 8:11 ` Prathamesh Kulkarni
2016-08-09 9:24 ` Richard Biener
2016-08-09 11:09 ` Martin Jambor
2016-08-09 11:47 ` Prathamesh Kulkarni
2016-08-09 18:13 ` Martin Jambor
2016-08-10 8:45 ` Prathamesh Kulkarni
2016-08-10 11:35 ` Prathamesh Kulkarni
2016-08-11 12:55 ` Jan Hubicka
2016-08-12 9:54 ` Prathamesh Kulkarni
2016-08-12 14:04 ` Jan Hubicka
2016-08-16 13:05 ` Prathamesh Kulkarni
2016-08-22 13:33 ` Martin Jambor
2016-08-22 13:55 ` Prathamesh Kulkarni
2016-08-24 12:07 ` Prathamesh Kulkarni
2016-08-25 13:44 ` Jan Hubicka
2016-08-26 12:31 ` Prathamesh Kulkarni
2016-08-26 16:23 ` Rainer Orth
2016-08-26 17:23 ` Prathamesh Kulkarni
2016-08-29 10:53 ` Christophe Lyon
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=20160804130549.GA77269@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.org \
--cc=mjambor@suse.cz \
--cc=prathamesh.kulkarni@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).