search for: gccbug

Patch A: (gccbug-v2-a.patch) It replaces fp code with integer. Basically it changed ceil(x * (1.-0.95)) with (x/20 + x%20?1:0). This also slightly changes calculated RG value, so test_replaygain.sh was also updated. Why RG value differs? Because double(1.-0.95) > double(0.05). If x==20 then ceil(x * (1.-0.95))...

...ll/bin# ls bugpoint gcc gcov i686-pc-linux-gnu-g++ lli llvmc llvm-extract llvm-prof tblgen c++ gccas i686-pc-linux-gnu-c++ i686-pc-linux-gnu-gcc llvm-ar llvm-config llvm-ld llvm-ranlib cpp gccbug i686-pc-linux-gnu-cpp i686-pc-linux-gnu-gcc-4.2.1 llvm-as llvm-db llvm-link llvm-stub g++ gccld i686-pc-linux-gnu-cpp-4.2.1 llc ―――――――――――――――――――――――――――――――――――――― The following is the result when I execute ./gcc -v : ――――――――――――――――――――――――――――...

...> ------------------------------- > After gunzip > * cfrontend-1.3.i386-unknown-freebsd5.2.1.tar.gz > and > * tar -xf cfrontend-1.3.i386-unknown-freebsd5.2.1.tar > I see that cfrontend/x86/llvm-gcc/bin contains the following files: > > c++ > cpp > g++ > gcc > gccbug > gcov > i386-unknown-freebsd5.2.1-c++ > i386-unknown-freebsd5.2.1-g++ > i386-unknown-freebsd5.2.1-gcc > i386-unknown-freebsd5.2.1-gcc-3.4-llvm > > Are they executables? > > Which of them should I use on Cygwin? Well, you shouldn't use any of these, as the FreeBSD...

...frontend-1.3.source.tar.gz ? 1. Question about executables. ------------------------------- After gunzip * cfrontend-1.3.i386-unknown-freebsd5.2.1.tar.gz and * tar -xf cfrontend-1.3.i386-unknown-freebsd5.2.1.tar I see that cfrontend/x86/llvm-gcc/bin contains the following files: c++ cpp g++ gcc gccbug gcov i386-unknown-freebsd5.2.1-c++ i386-unknown-freebsd5.2.1-g++ i386-unknown-freebsd5.2.1-gcc i386-unknown-freebsd5.2.1-gcc-3.4-llvm Are they executables? Which of them should I use on Cygwin? 2. Question about sources. -------------------------- http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.htm...

...gunzip > > * cfrontend-1.3.i386-unknown-freebsd5.2.1.tar.gz > > and > > * tar -xf cfrontend-1.3.i386-unknown-freebsd5.2.1.tar > > I see that cfrontend/x86/llvm-gcc/bin contains the following files: > > > > c++ > > cpp > > g++ > > gcc > > gccbug > > gcov > > i386-unknown-freebsd5.2.1-c++ > > i386-unknown-freebsd5.2.1-g++ > > i386-unknown-freebsd5.2.1-gcc > > i386-unknown-freebsd5.2.1-gcc-3.4-llvm > > > > Are they executables? > > > > Which of them should I use on Cygwin? > > Well,...

...gcc gcov i686-pc-linux-gnu-g++ > lli llvmc llvm-extract llvm-prof tblgen > c++ gccas i686-pc-linux-gnu-c++ i686-pc-linux-gnu-gcc > llvm-ar llvm-config llvm-ld llvm-ranlib > cpp gccbug i686-pc-linux-gnu-cpp i686-pc-linux-gnu-gcc-4.2.1 > llvm-as llvm-db llvm-link llvm-stub > g++ gccld i686-pc-linux-gnu-cpp-4.2.1 llc > —————————————————————————————————————— > > The following is the result when I execute ./gcc -v : &gt...

I checked out LLVM and configured like this: ./configure --prefix=/home/regehr --enable-optimized then built and installed it. Then, checked out the frontend, configured like this: ../configure --prefix=/home/regehr --enable-languages=c,c++ \ --enable-llvm=/home/regehr/z/llvm but when I try to build I get configure: error: You must specify valid path to your LLVM tree with

...t; > * cfrontend-1.3.i386-unknown-freebsd5.2.1.tar.gz > > and > > * tar -xf cfrontend-1.3.i386-unknown-freebsd5.2.1.tar > > I see that cfrontend/x86/llvm-gcc/bin contains the following files: > > > > c++ > > cpp > > g++ > > gcc > > gccbug > > gcov > > i386-unknown-freebsd5.2.1-c++ > > i386-unknown-freebsd5.2.1-g++ > > i386-unknown-freebsd5.2.1-gcc > > i386-unknown-freebsd5.2.1-gcc-3.4-llvm > > > > Are they executables? > > > > Which of them should I use on Cygwin? >...