On Sat, 26 May 2018, Bin.Cheng wrote:
> On Fri, May 25, 2018 at 5:54 PM, Richard Biener wrote:
> > On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law wrote:
> >>On 05/25/2018 03:49 AM, Bin.Cheng wrote:
> >>> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
> >>> wrote:
> On 23 May 2018 at
On Fri, May 25, 2018 at 5:54 PM, Richard Biener wrote:
> On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law wrote:
>>On 05/25/2018 03:49 AM, Bin.Cheng wrote:
>>> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
>>> wrote:
On 23 May 2018 at 18:37, Jeff Law wrote:
> On 05/23/2018 03:20
On May 25, 2018 9:25:51 PM GMT+02:00, Jeff Law wrote:
>On 05/25/2018 11:54 AM, Richard Biener wrote:
>> On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law
>wrote:
>>> On 05/25/2018 03:49 AM, Bin.Cheng wrote:
On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
wrote:
> On 23 May 2018
On 05/25/2018 11:54 AM, Richard Biener wrote:
> On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law wrote:
>> On 05/25/2018 03:49 AM, Bin.Cheng wrote:
>>> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
>>> wrote:
On 23 May 2018 at 18:37, Jeff Law wrote:
> On 05/23/2018 03:20 AM, Prath
On May 25, 2018 6:57:13 PM GMT+02:00, Jeff Law wrote:
>On 05/25/2018 03:49 AM, Bin.Cheng wrote:
>> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
>> wrote:
>>> On 23 May 2018 at 18:37, Jeff Law wrote:
On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
> On 23 May 2018 at 13:58, R
On 05/25/2018 03:49 AM, Bin.Cheng wrote:
> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
> wrote:
>> On 23 May 2018 at 18:37, Jeff Law wrote:
>>> On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
On 23 May 2018 at 13:58, Richard Biener wrote:
> On Wed, 23 May 2018, Prathamesh K
On Fri, 25 May 2018, Bin.Cheng wrote:
> On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
> wrote:
> > On 23 May 2018 at 18:37, Jeff Law wrote:
> >> On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
> >>> On 23 May 2018 at 13:58, Richard Biener wrote:
> On Wed, 23 May 2018, Prathamesh
On Fri, May 25, 2018 at 10:23 AM, Prathamesh Kulkarni
wrote:
> On 23 May 2018 at 18:37, Jeff Law wrote:
>> On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
>>> On 23 May 2018 at 13:58, Richard Biener wrote:
On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
> Hi,
> I am trying t
On 23 May 2018 at 18:37, Jeff Law wrote:
> On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
>> On 23 May 2018 at 13:58, Richard Biener wrote:
>>> On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
>>>
Hi,
I am trying to work on PR80155, which exposes a problem with code
hoisting and
On 05/23/2018 03:20 AM, Prathamesh Kulkarni wrote:
> On 23 May 2018 at 13:58, Richard Biener wrote:
>> On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
>>
>>> Hi,
>>> I am trying to work on PR80155, which exposes a problem with code
>>> hoisting and register pressure on a leading embedded benchmark
On Wed, May 23, 2018 at 9:28 AM, Richard Biener wrote:
> On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
>
>> Hi,
>> I am trying to work on PR80155, which exposes a problem with code
>> hoisting and register pressure on a leading embedded benchmark for ARM
>> cortex-m7, where code-hoisting causes
On 23 May 2018 at 13:58, Richard Biener wrote:
> On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
>
>> Hi,
>> I am trying to work on PR80155, which exposes a problem with code
>> hoisting and register pressure on a leading embedded benchmark for ARM
>> cortex-m7, where code-hoisting causes an extra
On Wed, 23 May 2018, Prathamesh Kulkarni wrote:
> Hi,
> I am trying to work on PR80155, which exposes a problem with code
> hoisting and register pressure on a leading embedded benchmark for ARM
> cortex-m7, where code-hoisting causes an extra register spill.
>
> I have attached two test-cases wh
Hi,
I am trying to work on PR80155, which exposes a problem with code
hoisting and register pressure on a leading embedded benchmark for ARM
cortex-m7, where code-hoisting causes an extra register spill.
I have attached two test-cases which (hopefully) are representative of
the original test-case.
14 matches
Mail list logo