[LLVMdev] Help needed on debugging llvm
Anitha B Gollamudi
anitha.boyapati at gmail.com
Mon Mar 11 04:28:35 PDT 2013
On 11 March 2013 16:13, Anitha B Gollamudi <anitha.boyapati at gmail.com> wrote:
> On 11 March 2013 10:06, Anitha B Gollamudi <anitha.boyapati at gmail.com> wrote:
>> On 23 January 2013 00:20, Craig Topper <craig.topper at gmail.com> wrote:
>>> Are you still having issues with FMA4? I wonder if PR15040 is related. A
>>> fix was just committed.
> Unfortunately r173176 does not fix this. I have updated the trunk and
> ran...Miscompare still persists.
> Going by http://llvm.org/bugs/show_bug.cgi?id=14185#c12 , I am
> inclined to think that it is an optimization. (If it is an encoding
> issue, dragonegg would have failed as well...). or maybe I am missing
> something here.
Ah, I am taking back my above words w.r.t encoding. -no-integrated-as
does fix the issue! This definitely points towards FMA4 encoding in
clang's integrated assembler. This fits into the analysis as well -
dragonegg *might not* be using integrated assembler at all.
Here is a log of my run that ended on happy note using
-no-integrated-as. Thanks Craig :-)
/local/home/anitha/cpu2006/bin/specinvoke -E -d /local/home/anitha/cpu2006/bench
spec/CPU2006/444.namd/run/run_peak_ref_llvm.0001 -c 1 -e compare.err -o compare.
stdout -f compare.cmd
Producing Raw Reports
format: raw -> /local/home/anitha/cpu2006/result/CFP2006.102.ref.rsf
Parsing flags for 444.namd peak: done
Doing flag reduction: done
format: flags -> /local/home/anitha/cpu2006/result/CFP2006.102.ref.flags
format: ASCII -> /local/home/anitha/cpu2006/result/CFP2006.102.ref.txt
format: HTML -> /local/home/anitha/cpu2006/result/CFP2006.102.ref.html,
The log for this run is in /local/home/anitha/cpu2006/result/CPU2006.102.log
More information about the llvm-dev