search for: specmaker

[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: u...

Hi, all I use llvm-gcc -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 |

In compiling perlbench in SPEC2006 today, I get the following asm code: .4byte ($debug_loc2280) .4byte 1 .4byte PerlIO_fd_refcnt $set1406 = ($.bss_end)-PerlIO_fd_refcnt .4byte ($set1406) .4byte PerlIO_perlio $set1407 = ($.data_end)-PerlIO_perlio .4byte ($set1407) .4byte ($func_begin0) $set1408 = ($.text_end)-($func_begin0) .4byte

On 2009-12-23 08:22, Li Shengmei wrote: > > Hi, all > > I use llvm-gcc –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

Hi Duncan I am facing a build error about __builtin_iceil 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

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

> >> 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 with the -native-cbe or -native options. Is there anything special flagwise that I would need to specify to tell it to include symbol and debug information?

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

On 6 November 2012 14:52, Duncan Sands <baldrick at free.fr> wrote: > Hi Anitha, > > > On 06/11/12 10:19, Anitha Boyapati wrote: > >> Hi Duncan >> I am facing a build error about __builtin_iceil >> > > 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

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

Hi Anitha, On 06/11/12 10:19, Anitha Boyapati wrote: > Hi Duncan > I am facing a build error about __builtin_iceil it's surely just that dragonegg doesn't have any support for this builtin. Please open a bug report with a minimal test case. Ciao, Duncan. when compiled > with dragonegg using -ffast-math option. My dragonegg is built with gcc-4.7.0 > (I am compiling namd

Actually I am trying to run SPEC2006 through the Makefiles provided with LLVM Test Suite, so I think it should work properly... On 18 February 2013 15:49, Adhemerval Zanella <azanella at linux.vnet.ibm.com>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

> > 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

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

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

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[2]...

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.