Re: Possible linearizer issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Luc,

On 21 March 2017 at 15:05, Luc Van Oostenryck
<luc.vanoostenryck@xxxxxxxxx> wrote:
> On Sat, Mar 18, 2017 at 11:41:26AM +0000, Dibyendu Majumdar wrote:
>> I am investigating a failure in one of the tests. The generated
>> linearized code has instructions such as:
>>
>> .L363:
>>  br          VOID, .L366, .L439
>> .L366:
>>  load.32     %r413 <- 44[%arg1]
>>  br          %r413, .L368, .L369
>> .L368:
>>  load.64     %r415 <- 0[s7813er]
>>  call.32     %r416 <- printf, %r415, $2
>>  br          .L369
>> .L369:
>>  phisrc.32   %phi97(rc) <- $2
>>  br          .L439
>> .L439:
>>  phi.32      %r557 <- %phi95(rc), VOID, %phi97(rc), VOID, VOID, VOID
>>
>> The test program is here:
>>
>> https://github.com/dibyendumajumdar/dmr_c/blob/master/tests/set1/cq2.c
>
> I have looked a bit at this.
> Reverting the patch (11b1a83b1 "fix OP_PHI usage in try_to_simplify_bb()")
> should fix this but I'm not 100% sure about the consequence.
> I'm looking for a proper solution though (but it need a bit infrastructure
> code that I first need to put in place, so it will take a bit time).
>

I can confirm that removing that patch did fix the issue.

Thanks and Regards
Dibyendu
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux