On Thu, Jan 22, 2015 at 7:04 PM, Jeff Law wrote:
>> Thanks for the review. Comments addressed and patch committed. The
>> problem exists on gcc-4_9 too. Is it ok for gcc-4_9-branch? Will wait
>> another day to commit it to gcc-4_9 if it is ok.
>
> Yes, if the patch from Uros was backported to 4.9
On 01/22/15 11:00, Wei Mi wrote:
Thanks for the review. Comments addressed and patch committed. The
problem exists on gcc-4_9 too. Is it ok for gcc-4_9-branch? Will wait
another day to commit it to gcc-4_9 if it is ok.
Yes, if the patch from Uros was backported to 4.9, then this patch
should get
Thanks for the review. Comments addressed and patch committed. The
problem exists on gcc-4_9 too. Is it ok for gcc-4_9-branch? Will wait
another day to commit it to gcc-4_9 if it is ok.
Thanks,
Wei.
On Thu, Jan 22, 2015 at 9:39 AM, Jeff Law wrote:
> On 01/21/15 15:32, Wei Mi wrote:
>>
>> Hi,
>>
On 01/21/15 15:32, Wei Mi wrote:
Hi,
The patch is to address the bug here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64557
It is to call get_addr for VALUE before forming a mem_addr expr with
the VALUE and an offset. This is to avoid the problem that get_addr
can only handle VALUE but cannot