Displaying 3 results from an estimated 3 matches for "specinvoke".
2010 Jul 05
0
[LLVMdev] likely SPECCPU2006 miscompilation
Using clang r107598 at -O1 to create reportable SPECINT 2006 results, I'm
getting the output below, which is almost certainly due to a
miscompilation. Known problem?
Thanks,
John
Running (#3) 403.gcc ref base i386-m32-gcc42-nn default
/home/regehr/z/specCPU2006/bin/specinvoke -d
/home/regehr/z/specCPU2006/benchspec/CPU2006/403.gcc/run/run_base_ref_i386-m32-gcc42-nn.0000
-e speccmds.err -o speccmds.stdout -f speccmds.cmd -C
403.gcc: copy #0 non-zero return code (rc=1, signal=0)
****************************************
Contents of c-typeck.err
***********************...
2013 Mar 11
0
[LLVMdev] Help needed on debugging llvm
...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
Success: 1x444.namd
Producing Raw Reports
mach: default
ext: llvm
size: ref
set: int
set: fp
format: raw -> /local/home/anitha/c...
2013 Mar 11
2
[LLVMdev] Help needed on debugging llvm
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.