[LLVMdev] Help needed on debugging llvm

[Duncan Sands]

Hi Anitha,

>     it's surely just that dragonegg doesn't have any support for this builtin.
>
> ok. Just verified that Target.cpp and x86_builtins do not have iceil support.
> I have this tricky situation - I use dragonegg generated LLVM IR as input to
> clang for some analysis (well it is clang++ actually). Understably,clang cribs
> looking at __builtin_iceil. Any idea how to resolve that as well?

adding dragonegg support for iceil would solve both problems.

Ciao, Duncan.

> clang++   -O2 -march=bdver2 -mno-fma -save-temps  -mfma4 -ffp-contract=fast
> -DSPEC_CPU_LP64        Compute.o ComputeList.o ComputeNonbondedUtil.o LJTable.o
> Molecule.o Patch.o PatchList.o ResultSet.o SimParameters.o erf.o
> spec_namd.o                     -o namd
> spec_namd.o: In function `main':
> spec_namd.ll:(.text+0x2a3): undefined reference to `__builtin_iceil'
>
>     Please open a bug report with a minimal test case
>
> Will do. Thanks
> -Anitha
>
>     Ciao, Duncan.
>
>       when compiled
>
>         with dragonegg using -ffast-math option. My dragonegg is built with
>         gcc-4.7.0
>         (I am compiling namd spec benchmark here again).
>         Any idea?
>         g++ -march=bdver2 -save-temps
>         -fplugin=/home/anboyapa/__install/bin/dragonegg.so
>         -O2 -march=bdver2 -save-temps
>         -fplugin=/home/anboyapa/__install/bin/dragonegg.so
>         -mno-fma -mfma4 -ffast-math  -DSPEC_CPU_LP64        Compute.o ComputeList.o
>         ComputeNonbondedUtil.o LJTable.o Molecule.o Patch.o PatchList.o ResultSet.o
>         SimParameters.o erf.o spec_namd.o                     -o namd
>         spec_namd.o: In function `main':
>         spec_namd.C:(.text+0x2a3): undefined reference to `__builtin_iceil'
>         collect2: error: ld returned 1 exit status
>         specmake: *** [namd] Error 1
>
>
>         On 5 November 2012 14:32, Duncan Sands <baldrick at free.fr
>         <mailto:baldrick at free.fr>
>         <mailto:baldrick at free.fr <mailto:baldrick at free.fr>>> wrote:
>
>              Hi Anitha,
>
>
>         http://llvm.org/bugs/show_bug.____cgi?id=14185
>         <http://llvm.org/bugs/show_bug.__cgi?id=14185>
>
>                  <http://llvm.org/bugs/show___bug.cgi?id=14185
>         <http://llvm.org/bugs/show_bug.cgi?id=14185>>
>                  I am stuck on analysis. Does any one have alternate suggestions
>         on debugging
>                  llvm? (Please refer to comments for the work done so far)
>
>
>              try to reduce a small standalone testcase which is an LLVM IR (.ll)
>         file.
>
>              Ciao, Duncan.
>
>              ___________________________________________________
>              LLVM Developers mailing list
>         LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu>
>         <mailto:LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu>>
>         http://llvm.cs.uiuc.edu
>         http://lists.cs.uiuc.edu/____mailman/listinfo/llvmdev
>         <http://lists.cs.uiuc.edu/__mailman/listinfo/llvmdev>
>              <http://lists.cs.uiuc.edu/__mailman/listinfo/llvmdev
>         <http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>>
>
>
>
>
>         --
>         /* Anitha*/
>
>
>
>
>
> --
> /* Anitha*/
>