similar to: [LLVMdev] Help needed after hiatus

The problem was solved by setting environment variable CXX. But somehow a new one came. The gcc is installed in /usr/local/gcc-4.2.3. I managed to change clang/lib/Frontend/InitHeaderSearch.cpp clang/lib/Driver/ToolChains.cpp to force clang use the crt lib for that version. For details, plz see http://www.advogato.org/person/redi/diary/228.html. So now I have no problem of using clang to

I'm a little further along now. I've started to put together a simple driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think it works). The file being compiled is a "printf" function. Here are timing results for optimized and unoptimized runs: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i -time-actions Adding test/ofmt.i as a preprocessed C file

Hi all, I wanted to install R under a sunOs machine, so I launched the configuration with the following command: "./configure --prefix /sw/gnu/R/R-2.1.0/sun/ --with-readline=no" The rsult of this configuration seemed good " R is now configured for sparc-sun-solaris2.8 Source directory: . Installation directory: /sw/gnu/R/R-2.1.0/sun/ C compiler:

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

Hi, I know my last question was very vague (i.e. "It stopped working, what went wrong?"), so here is a little more concrete example: If I run the optimizer (opt) on this code snippet with -std-compile-opts the optimizer hangs. ; ModuleID = 'test.ubc' target datalayout =

Hi, I'ma having some troubles installing R under Unix. As it is written in the "how to install R" the ./configure passed on but when I type make I recieve this error message : gmake[1]: Entering directory `/usr/local/R_HOME/R-2.4.0/m4' gmake[1]: Nothing to be done for `R'. gmake[1]: Leaving directory `/usr/local/R_HOME/R-2.4.0/m4' gmake[1]: Entering directory

On 12/21/07, Richard Pennington <rich at pennware.com> wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). Er. Hm. Can you explain the name? The problem with names like "ellsif" is that it sounds like "else if". I like the

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once!

I am trying to compile R-devel (R-devel_2006-05-17.tar.gz) on Red Hat Enterprise Linux AS release 3 (Taroon Update 7) using the Portland Group compiler 6.0. (I have not yet successful compiled R on this configuration, so I don't know if this is a new problem.) I get an error pgcc -L/usr/local/pgi/linux86-64/6.0/libso -L/usr/lib64 -o dftables dftables.o ../dftables chartables.h

Dear friends, I am trying to install R-2.4.1 from source on Solaris 11 x-86. 64 bits, running on Sun Ultra-20 workstation, and using the SunStudio 11 compilers. I was able to "configure" R correctly, but received an error in "gmake", aparently related to bzip2 which I have been unable to debug. The messages are listed below. The configure.log and configure.status files are

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument

Chris Lattner wrote: > On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote: > >> I'm a little further along now. I've started to put together a simple >> driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think >> it works). >> >> The file being compiled is a "printf" function. Here are timing >> results

On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote: > I'm a little further along now. I've started to put together a simple > driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think > it works). > > The file being compiled is a "printf" function. Here are timing > results > for optimized and unoptimized runs: Cool, this is

Jay Foad wrote: >> I'm linking a program (my ellsif driver) that basically brings in most >> of the LLVM stuff: bitcode reading, optimizations, linking, and target >> code generation. >> >> All of a sudden, I'm getting the following when I run: >> [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions >> -O5 >>

Are you saying this is this the first time you've tried to compile it on the cluster? It's easy to determine if g++ is installed and in the PATH - just get a console on the cluster and type "g++". However, AFAIK cluster nodes are not usually configured for software development, are they? Typically you build your code locally and then job it out to the cluster? Greg

I've compiled llvm several times, but this is the first time I saw this error when I was trying to compile it in a cluster. checking tool compatibility... configure: error: g++|clang++|icc required but not found I am pretty sure g++ is installed and in the path. I then downloaded clang++ binary and set path. The error was still there. OS: opensuse 10.1 gcc, g++ version: 4.2.3 Any idea? Bo

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/

Hi all, I've encountered a build error with the latest R source (2.8.1). This is a relatively fresh install of OS Leopard (10.5.6), latest developer tools installed, gcc/g++/gfortran version 4.4 installed (via http://hpc.sourceforge.net/, after which I updated the gcc & g++ symlinks to link to the 4.4 versions; gfortran used the 4.4 version without updating the symlink). Ultimately I

I found how to build CRC32 table for Ogg in JS, if anyone interested: function _makeCRC32Table() { // From https://stackoverflow.com/questions/53438815/hot-to-build-crc32-table-for-ogg const polynomial = 79764919; const mask = 2147483648; const CRCTable = new Uint32Array(256); for (let i = 256; i--;) { let char = i << 24; for (let j = 8; j--;) {

> I've build gcc many times over the years for different target processors > and was never able to get my head around it internally. It is incredibly > complex. I also didn't like the fact that I had to have N copies of gcc > to support N processors. Scott McPeak is rather familiar with the internals of gcc and edg and says elsa is far simpler. > I became interested in