On 26 August 2016 at 19:22, Prathamesh Kulkarni
wrote:
> On 26 August 2016 at 21:53, Rainer Orth wrote:
>> Hi Prathamesh,
>>
>>> The attached version passes bootstrap+test on
>>> x86_64-unknown-linux-gnu, ppc64le-linux-gnu,
>>> and with c,c++,fortran on armv8l-linux-gnueabihf.
>>> Cross-tested on
On 26 August 2016 at 21:53, Rainer Orth wrote:
> Hi Prathamesh,
>
>> The attached version passes bootstrap+test on
>> x86_64-unknown-linux-gnu, ppc64le-linux-gnu,
>> and with c,c++,fortran on armv8l-linux-gnueabihf.
>> Cross-tested on arm*-*-* and aarch64*-*-*.
>> Verified the patch survives lto-b
Hi Prathamesh,
> The attached version passes bootstrap+test on
> x86_64-unknown-linux-gnu, ppc64le-linux-gnu,
> and with c,c++,fortran on armv8l-linux-gnueabihf.
> Cross-tested on arm*-*-* and aarch64*-*-*.
> Verified the patch survives lto-bootstrap on x86_64-unknown-linux-gnu.
> Ok to commit ?
[
On 25 August 2016 at 19:14, Jan Hubicka wrote:
>> Patch for performing interprocedural bitwise constant propagation.
>>
>> 2016-08-23 Prathamesh Kulkarni
>> Martin Jambhor
>>
>> * common.opt: New option -fipa-cp-bit.
>> * doc/invoke.texi: Document -fipa-cp-bit.
>>
> Patch for performing interprocedural bitwise constant propagation.
>
> 2016-08-23 Prathamesh Kulkarni
> Martin Jambhor
>
> * common.opt: New option -fipa-cp-bit.
> * doc/invoke.texi: Document -fipa-cp-bit.
> * opts.c (default_options_table): Add entry for -fipa-
On 22 August 2016 at 19:24, Prathamesh Kulkarni
wrote:
> On 22 August 2016 at 19:03, Martin Jambor wrote:
>> Hi,
>>
>> On Tue, Aug 16, 2016 at 06:34:48PM +0530, Prathamesh Kulkarni wrote:
>>> Thanks, I updated the patch to address these issues (attached).
>>> However the patch caused ICE during t
On 22 August 2016 at 19:03, Martin Jambor wrote:
> Hi,
>
> On Tue, Aug 16, 2016 at 06:34:48PM +0530, Prathamesh Kulkarni wrote:
>> Thanks, I updated the patch to address these issues (attached).
>> However the patch caused ICE during testing
>> objc.dg/torture/forward-1.m (and few others but with
Hi,
On Tue, Aug 16, 2016 at 06:34:48PM +0530, Prathamesh Kulkarni wrote:
> Thanks, I updated the patch to address these issues (attached).
> However the patch caused ICE during testing
> objc.dg/torture/forward-1.m (and few others but with same ICE):
>
> Command line options:
> /home/prathamesh.k
On 12 August 2016 at 19:33, Jan Hubicka wrote:
>> On 11 August 2016 at 18:25, Jan Hubicka wrote:
>> >> @@ -266,6 +267,38 @@ private:
>> >>bool meet_with_1 (unsigned new_align, unsigned new_misalign);
>> >> };
>> >>
>> >> +/* Lattice of known bits, only capable of holding one value.
>> >> +
> On 11 August 2016 at 18:25, Jan Hubicka wrote:
> >> @@ -266,6 +267,38 @@ private:
> >>bool meet_with_1 (unsigned new_align, unsigned new_misalign);
> >> };
> >>
> >> +/* Lattice of known bits, only capable of holding one value.
> >> + Similar to ccp_lattice_t, mask represents which bits o
On 11 August 2016 at 18:25, Jan Hubicka wrote:
>> @@ -266,6 +267,38 @@ private:
>>bool meet_with_1 (unsigned new_align, unsigned new_misalign);
>> };
>>
>> +/* Lattice of known bits, only capable of holding one value.
>> + Similar to ccp_lattice_t, mask represents which bits of value are
>
> @@ -266,6 +267,38 @@ private:
>bool meet_with_1 (unsigned new_align, unsigned new_misalign);
> };
>
> +/* Lattice of known bits, only capable of holding one value.
> + Similar to ccp_lattice_t, mask represents which bits of value are
> constant.
> + If a bit in mask is set to 0, then
On 10 August 2016 at 14:14, Prathamesh Kulkarni
wrote:
> On 9 August 2016 at 23:43, Martin Jambor wrote:
>> Hi,
>>
>> On Tue, Aug 09, 2016 at 05:17:31PM +0530, Prathamesh Kulkarni wrote:
>>> On 9 August 2016 at 16:39, Martin Jambor wrote:
>>>
>>> ...
>>>
>>> >> Instead of storing arg's precision
On 9 August 2016 at 23:43, Martin Jambor wrote:
> Hi,
>
> On Tue, Aug 09, 2016 at 05:17:31PM +0530, Prathamesh Kulkarni wrote:
>> On 9 August 2016 at 16:39, Martin Jambor wrote:
>>
>> ...
>>
>> >> Instead of storing arg's precision and sign, we should store
>> >> parameter's precision and sign in
Hi,
On Tue, Aug 09, 2016 at 05:17:31PM +0530, Prathamesh Kulkarni wrote:
> On 9 August 2016 at 16:39, Martin Jambor wrote:
>
> ...
>
> >> Instead of storing arg's precision and sign, we should store
> >> parameter's precision and sign in ipa_compute_jump_functions_for_edge ().
> >> Diff with resp
On 9 August 2016 at 16:39, Martin Jambor wrote:
> Hi,
>
> On Tue, Aug 09, 2016 at 01:41:21PM +0530, Prathamesh Kulkarni wrote:
>> On 8 August 2016 at 19:33, Martin Jambor wrote:
>> >> >> +class ipcp_bits_lattice
>> >> >> +{
>> >> >> +public:
>> >> >> + bool bottom_p () { return lattice_val == IP
Hi,
On Tue, Aug 09, 2016 at 01:41:21PM +0530, Prathamesh Kulkarni wrote:
> On 8 August 2016 at 19:33, Martin Jambor wrote:
> >> >> +class ipcp_bits_lattice
> >> >> +{
> >> >> +public:
> >> >> + bool bottom_p () { return lattice_val == IPA_BITS_VARYING; }
> >> >> + bool top_p () { return lattice
On Tue, 9 Aug 2016, Prathamesh Kulkarni wrote:
> On 8 August 2016 at 19:33, Martin Jambor wrote:
> > Hi,
> >
> > thanks for following through. You'll need an approval from Honza, but
> > I think the code looks good (I have looked at the places that I
> > believe have changed since the last week)
On 8 August 2016 at 19:33, Martin Jambor wrote:
> Hi,
>
> thanks for following through. You'll need an approval from Honza, but
> I think the code looks good (I have looked at the places that I
> believe have changed since the last week). However, I have discovered
> one new thing I don't like a
On Mon, 2016-08-08 at 16:03 +0200, Martin Jambor wrote:
> Hi,
>
> thanks for following through. You'll need an approval from Honza,
> but
> I think the code looks good (I have looked at the places that I
> believe have changed since the last week). However, I have
> discovered
> one new thing I
Hi,
thanks for following through. You'll need an approval from Honza, but
I think the code looks good (I have looked at the places that I
believe have changed since the last week). However, I have discovered
one new thing I don't like and still believe you need to handle
different precisions in
On 5 August 2016 at 18:06, Martin Jambor wrote:
> Hi,
Hi Martin,
Thanks for the review. Please find my responses inline.
>
> generally speaking, the ipa-cp.c and ipa-cp.[hc] bits look reasonable,
> but I have a few comments:
>
> On Thu, Aug 04, 2016 at 12:06:18PM +0530, Prathamesh Kulkarni wrote:
Hi,
generally speaking, the ipa-cp.c and ipa-cp.[hc] bits look reasonable,
but I have a few comments:
On Thu, Aug 04, 2016 at 12:06:18PM +0530, Prathamesh Kulkarni wrote:
> Hi,
> This is a prototype patch for propagating known/unknown bits
> inter-procedurally.
> for integral types which propaga
> Hi Honza,
>
> On 04/08/16 23:05, Jan Hubicka wrote:
> >>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 rep
Hi Honza,
On 04/08/16 23:05, Jan Hubicka wrote:
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 propag
> 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
On Thu, 4 Aug 2016, Prathamesh Kulkarni wrote:
> On 4 August 2016 at 13:31, Richard Biener wrote:
> > On Thu, 4 Aug 2016, Prathamesh Kulkarni wrote:
> >
> >> Hi,
> >> This is a prototype patch for propagating known/unknown bits
> >> inter-procedurally.
> >> for integral types which propagates in
On 04/08/16 18:57, Prathamesh Kulkarni wrote:
On 4 August 2016 at 13:31, Richard Biener wrote:
On Thu, 4 Aug 2016, Prathamesh Kulkarni wrote:
Hi,
This is a prototype patch for propagating known/unknown bits inter-procedurally.
for integral types which propagates info obtained from get_nonze
On 4 August 2016 at 13:31, Richard Biener wrote:
> On Thu, 4 Aug 2016, Prathamesh Kulkarni wrote:
>
>> Hi,
>> This is a prototype patch for propagating known/unknown bits
>> inter-procedurally.
>> for integral types which propagates info obtained from get_nonzero_bits ().
>>
>> Patch required mak
On Thu, 4 Aug 2016, Prathamesh Kulkarni wrote:
> Hi,
> This is a prototype patch for propagating known/unknown bits
> inter-procedurally.
> for integral types which propagates info obtained from get_nonzero_bits ().
>
> Patch required making following changes:
> a) To make info from get_nonzero_
Hi,
This is a prototype patch for propagating known/unknown bits inter-procedurally.
for integral types which propagates info obtained from get_nonzero_bits ().
Patch required making following changes:
a) To make info from get_nonzero_bits() available to ipa, I had to remove
guard !nonzero_p in cc
31 matches
Mail list logo
