search for: specmak

[root@fnord-rides-again wine]# make make[1]: Entering directory `/root/wine/unicode' make[1]: `libwine_unicode.so' is up to date. make[1]: Leaving directory `/root/wine/unicode' make[1]: Entering directory `/root/wine/tools' make[2]: Entering directory `/root/wine/tools/specmaker' gcc -g -O2 -Wall -o specmaker dll.o main.o misc.o msmangle.o output.o search.o symbol.o dll.o: In function `dll_open': /root/wine/tools/specmaker/dll.c:83: undefined reference to `atexit' output.o: In function `output_spec_preamble': /root/wine/tools/specmaker/output.c:30:...

...-O4 to compile SPEC 2000, some benchmarks can't be built successfully, such as 164.gzip, 175.vpr etc. The error messages are as follows. .. zh.o unlzw.o unpack.o unzip.o util.o zip.o -o gzip bits.o: file not recognized: File format not recognized collect2: ld returned 1 exit status specmake: *** [gzip] Error 1 specmake options 2> options.err | tee options.out COMP: /home2/lishengmei/tools/llvm-gcc-4.2/bin/llvm-gcc -c -o options.o -O4 LINK: /home2/lishengmei/tools/llvm-gcc-4.2/bin/llvm-gcc -o options Some files did not appear to be built: gzip *** Error build...

....4byte ($func_begin0) $set1408 = ($.text_end)-($func_begin0) .4byte ($set1408) Gas complains: perlio.s: Assembler messages: perlio.s:43549: Error: operation combines symbols in different segments clang: error: assembler command failed with exit code 1 (use -v to see invocation) specmake: *** [perlio.o] Error 1 specmake: *** Waiting for unfinished jobs.... regexec.c:3275:111: warning: use of logical '||' with constant operand [-Wconstant This is on the line $set1406 = ($.bss_end)-PerlIO_fd_refcnt .bss $.bss_end: .section .rodata.str1.1,"aMS", a...

...LLVM bitcode, instead of ELF files, thus requires a linker that is able to understand it (such as the Gold linker, with the LLVM plugin). Try compiling any C source file with -O4, it won't work unless you have special support from the linker. > collect2: ld returned 1 exit status > > specmake: *** [gzip] Error 1 > > specmake options 2> options.err | tee options.out > > COMP: /home2/lishengmei/tools/llvm-gcc-4.2/bin/llvm-gcc -c -o > options.o -O4 > > LINK: /home2/lishengmei/tools/llvm-gcc-4.2/bin/llvm-gcc > -o options > > Some files...

...uteList.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> wrote: > Hi Anitha, > > > 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 suggestion...

Hi, I would like to use a TI dll used to communicate with TMS 320C6211 DSK with my own program written under Linux. Does anybody knows if it is possible (and how) to use (link) a Windows dll in a Linux program ?? Ciao, Riccardo Cerulli-Irelli

...tell it to include symbol and debug information? I've tried specifying -g but this information still doesn't seem to be included. A quick copy of the build of one of the tests to make sure I've got the flags right: Compiling Binaries Building 164.gzip ref base ppc32_llvm default specmake clean 2> make.err | tee make.out rm -rf gzip gzip.exe *.o core *.err *.out specmake build 2> make.err | tee make.out /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o bits.o -g -O3 bits.c /Users/patrick/Desktop/LLVM/cfrontend/ppc/llvm-gcc/bin/gcc -c -o deflat...

On Fri, 30 Apr 2004, Patrick Flanagan wrote: > Thanks! Grabbed the latest from CVS and added that linker option to the > config file. It looks like it compiles and runs the SPEC tests ok now. Great! > Just to make sure I understand how LLVM works, got a few clarifications: > > 1. The ppc code I'm generating with the -native-cbe is static, correct? Yes, it's purely static

...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>> wrote: >> >> Hi Anitha, >> >> >> http://llvm.org/bugs/show_bug.**__cgi?id=14185<http://llvm.org...

I can't really tell what is happening based on this output, but 'make' is not the right way to build SPECcpu2006 components. You need to do either by using the supplied 'runspec' command with '-build' action directive or to issue the 'specmake' (which is a make adjusted by spec.org) on the build component folder. I can build 433.milc on PPC64 with clang without any issue. On 02/18/2013 02:26 PM, Izabela Maffra wrote: > Dear LLVMers, > > I am having trouble to run SPEC2006. I have checked in my log file that the spec root...

...dUtil.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>> wrote: > > Hi Anitha, > > > http://llvm.org/bugs/show_bug.__cgi?id=14185 > <http://llvm.org/bugs/show_bug.cgi?id=14...

...wrote: > I can't really tell what is happening based on this output, but 'make' is > not the right way > to build SPECcpu2006 components. You need to do either by using the > supplied 'runspec' > command with '-build' action directive or to issue the 'specmake' (which > is a > make adjusted by spec.org) on the build component folder. > > I can build 433.milc on PPC64 with clang without any issue. > > On 02/18/2013 02:26 PM, Izabela Maffra wrote: > > Dear LLVMers, > > > > I am having trouble to run SPEC2006. I have...

> > There are two problems with this: 1) there is no JIT for PPC yet, so > LLVM will use the interpreter (which is intolerably slow and has other > issues). 2) Spec compiles the executables in one place and them moves > them to another, but it only copies the shell script and not the > bytecode file, so you get that error message. > > The normal solution to this problem

Thanks Jonas, I wasn't aware of the gold linker plugin. Here's what I do, in my current workflow. First, I use clang to compile each .c file (e.g. for the bzip2 benchmark, or any other) into a .bc file: specmake clean 2> make.clean.err | tee make.clean.out rm -rf bzip2 bzip2.exe *.o *.fppized.f* find . \( -name \*.o -o -name '*.fppized.f*' \) -print | xargs rm -rf rm -rf core specmake build 2> make.err | tee make.out clang -g -std=c89 -D_GNU_SOURCE -c -emit-llvm -c -o spec.o -DS...

Dear LLVMers, I am having trouble to run SPEC2006. I have checked in my log file that the spec root has been correctly found with ./configure, but when I try: make TEST=simple in the External folder I get the following error: make -C /home/izabela/svn_llvm/llvm/projects/test-suite/tools all \ ORIGINAL_CC="clang" \ ORIGINAL_CXX="clang" make[1]: Entering directory

...chList.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, > > >...

Hi, It was suggested that I post my question regarding a LLVM 3.4 performance regression to this mailing list, rather than stackoverflow. So here is the link: https://stackoverflow.com/questions/22902034/llvm-3-4-performance-regressed Thanks :) Jens -- Jens Tröger http://savage.light-speed.de/

...tput : make[1]: Entre dans le r?pertoire `/home/j/src/wine/unicode' make[1]: `libwine_unicode.so' est ? jour. make[1]: Quitte le r?pertoire `/home/j/src/wine/unicode' make[1]: Entre dans le r?pertoire `/home/j/src/wine/tools' make[2]: Entre dans le r?pertoire `/home/j/src/wine/tools/specmaker' make[2]: Rien ? faire pour `all'. make[2]: Quitte le r?pertoire `/home/j/src/wine/tools/specmaker' make[2]: Entre dans le r?pertoire `/home/j/src/wine/tools/winebuild' make[2]: Rien ? faire pour `all'. make[2]: Quitte le r?pertoire `/home/j/src/wine/tools/winebuild' make[...

Where could I get information about wine libraries content ? For instance, if I'm migrating a WNT console based application using winelib, which is the library I must link with object files ? I don't have this information. Thanks in advance. Ignasi Villagrasa.

Hi Anitha, > 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.