> On Thu, May 4, 2017 at 11:04 AM, Jan Hubicka wrote:
> >> >
> >> >Sure, I'm not questioning the patch, just wondering if we shouldn't
> >> >improve
> >> >store-merging further (we want to do it anyway for e.g. bitop adjacent
> >> >operations etc.).
> >>
> >> We definitely want to do that. It sho
On Thu, May 4, 2017 at 11:04 AM, Jan Hubicka wrote:
>> >
>> >Sure, I'm not questioning the patch, just wondering if we shouldn't
>> >improve
>> >store-merging further (we want to do it anyway for e.g. bitop adjacent
>> >operations etc.).
>>
>> We definitely want to do that. It should also 'nicely
> >
> >Sure, I'm not questioning the patch, just wondering if we shouldn't
> >improve
> >store-merging further (we want to do it anyway for e.g. bitop adjacent
> >operations etc.).
>
> We definitely want to do that. It should also 'nicely' merge with bswap for
> gathering the load side of a piec
On May 3, 2017 6:46:05 PM GMT+02:00, Jakub Jelinek wrote:
>On Wed, May 03, 2017 at 06:44:46PM +0200, Richard Biener wrote:
>> On May 3, 2017 6:22:14 PM GMT+02:00, Jakub Jelinek
>wrote:
>> >On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
>> >> Hi,
>> >> my change to sreals makes GCC t
On Wed, May 03, 2017 at 06:44:46PM +0200, Richard Biener wrote:
> On May 3, 2017 6:22:14 PM GMT+02:00, Jakub Jelinek wrote:
> >On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
> >> Hi,
> >> my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0.
> > This is
> >> related t
On Wed, May 03, 2017 at 06:39:18PM +0200, Jan Hubicka wrote:
> > On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
> > > Hi,
> > > my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0.
> > > This is
> > > related to fact that using sreal implies a non-trivial constructo
On May 3, 2017 6:22:14 PM GMT+02:00, Jakub Jelinek wrote:
>On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
>> Hi,
>> my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0.
> This is
>> related to fact that using sreal implies a non-trivial constructor
>and thus
>> ggc_c
> On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
> > Hi,
> > my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0. This
> > is
> > related to fact that using sreal implies a non-trivial constructor and thus
> > ggc_cleared_alloc is no longer standard compliant. I ho
On Wed, May 03, 2017 at 06:18:08PM +0200, Jan Hubicka wrote:
> Hi,
> my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0. This is
> related to fact that using sreal implies a non-trivial constructor and thus
> ggc_cleared_alloc is no longer standard compliant. I however do not qu
Hi,
my change to sreals makes GCC to be miscompiled with GCC 4.1 and -O0. This is
related to fact that using sreal implies a non-trivial constructor and thus
ggc_cleared_alloc is no longer standard compliant. I however do not quite
understand
why GCC 4.1 manages to misoptimize this code but I ha
10 matches
Mail list logo