[llvm-dev] Regression in SPEC2006/gcc caused by LoopLoadElimination

Adam Nemet via llvm-dev llvm-dev at lists.llvm.org
Wed Mar 9 16:17:26 PST 2016


I’ve committed the fix in r263058.  Haicheng, Eric/Benjamin, can you guys please give it a test with your codebase.  (You need to enable the pass with -mllvm -enable-loop-load-elim.)

Thanks!
Adam

> On Mar 7, 2016, at 11:05 PM, Adam Nemet <anemet at apple.com> wrote:
> 
> 
>> On Mar 7, 2016, at 9:43 AM, Adam Nemet <anemet at apple.com <mailto:anemet at apple.com>> wrote:
>> 
>> Hi Haicheng,
>> 
>> Sorry about the breakage.  I reverted it in r262839.
>> 
>> I will try to reproduce it locally.  Please don’t blow away your directories yet in case I need further help.
> 
> OK, I managed to reproduce this locally.  Should be able to make progress from here without further help from you.
> 
> Adam
> 
>> Thanks,
>> Adam
>> 
>>> On Mar 7, 2016, at 8:33 AM, Haicheng Wu <haicheng at codeaurora.org <mailto:haicheng at codeaurora.org>> wrote:
>>> 
>>> Hi Adam,
>>>  
>>> I find LoopLoadElimination (r262250) causes SPEC2006/gcc generate wrong result (166.s) in AArch64 when running with *ref* data set.  The error happens when I use either “-Ofast -flto -fuse-ld=gold” or “-O3 -fno-strict-aliasing”.  Please let me know if you need more information.
>>>  
>>> Best,
>>>  
>>> Haicheng
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160309/a19167d3/attachment.html>


More information about the llvm-dev mailing list