similar to: envelope.c CVS vorbis compile error.

Wow, I've never seen an FSF gcc crap out like this on a non-overheating system. When lib/envelope.c is compiled with -march=i686, gcc gets a signal 11, but not with -march=i586. I'm not sure whether to blame gcc or libvorbis. There are apparently three other files in libvorbis where this same behavior is seen. jeffrey@diddl:/usr/src/build/libvorbis-1.0/lib$ gcc

Hi all, I was just trying to build myself a RC3 set of Ogg/Vorbis libs and tools, but the build of libvorbis bombs out on me while making all in examples. I've ./configure'd with no options, which gave no warnings or errors. After that a normal make gives the below attached output. Can anyone tell me what I've done wrong ? I've also tried removing the examples/ directory. After

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

This is a linux from scratch based on the 2.4.13 kernel. I'm using a GCC 2.95.3, autoconf 2.52, and automake 1.5. Libvorbis compilation fails with a Signal 11 error as shown below. I had the same results with 2.4.12, 2.4.10, and 2.4.9. I've compiled hundreds of other packages without getting this error, and I've even tried changing the memory. This is my configure line, I used

I'm haivng trouble compiling the libvoribis source. I'm getting errors I don't understand, could somebody please look at the below and tell me if they have any ideas?? <p>make[2]: Entering directory `/root/libvorbis-1.0/lib' source='mdct.c' object='mdct.lo' libtool=yes \ depfile='.deps/mdct.Plo' tmpdepfile='.deps/mdct.TPlo' \ depmode=gcc3

I am running Linux Mandrake 7.2 with the following: platform i586-pc-linux-gnu arch i586 os linux-gnu system i586, linux-gnu status major 1 minor 2.3 year 2001 month 04 day 26 language R To build a package I ran R CMD build Hmisc, apparently with success: * checking for file `Hmisc/DESCRIPTION' ... OK * preparing `Hmisc': * cleaning src * checking

Some of the run commandlines don't seem to be the *default ref* configuration. For instance, in 099.go, what's in the script is: LEVEL = ../../../.. BM=099.go ifeq ($(RUN_TYPE),test) STDIN_FILENAME = /dev/null STDOUT_FILENAME = null.out RUN_OPTIONS = 40 19 else STDIN_FILENAME = 2stone9.in STDOUT_FILENAME = 2stone9.out RUN_OPTIONS = 50 9 endif include ../../Makefile.spec95

On Thu, 21 Jul 2005, Long Fei wrote: > Does anyone know the "standard" commandline to compile and run spec95 > benchmarks ? > > I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not > sure if they are the *default ref* configurations. <Some of them seem to use > smaller problem sizes.> SPEC95 was retired many years ago, so few people

On Thu, 21 Jul 2005, Long Fei wrote: > which suggests the compiling command: > gcc -DSPEC_CPU95 -O2 -o spec_go g2.c g22.c g23.c g25.c g26.c g27a.c g27b.c > g28.c g29.c g2eye.c g2jlib2.c g2jos.c g2list.c g2reas.c g2s2.c g2s3.c g2shp.c > and the running commandline: > ./spec_go 50 9 2stone9.in > < are these correct ? > I believe that we only include test/train inputs for

----- Original Message ----- > Hi Evan, > > We did an experiment using the LLVM test suite: we compare the > overhead of using our analysis to the LLVM default, both with -O2 > option. It might also be interesting to try with -O3; I don't know if we have any significant vectorizable loops in the test suite with a large number of arrays, but if we do, this kind of analysis

On Tue, Oct 22, 2013 at 9:55 AM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > Hi Evan, > > > > We did an experiment using the LLVM test suite: we compare the > > overhead of using our analysis to the LLVM default, both with -O2 > > option. > > It might also be interesting to try with -O3; I don't know if we have any

current Vorbis cvs gives: gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0\" -DHAVE_DLFCN_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -I. -I. -I../include -O20 --fast-math -mno-ieee-fp -D_REENTRANT -fsigned-char -O2 -march=i686 -mcpu=i686 -DUSE_MEMORY_H -Wp,-MD,.deps/envelope.cpp -c envelope.c -fPIC -DPIC -o .libs/envelope.lo gcc: Internal compiler error: program cc1 got fatal

My ogg library is located in /home/warren/local. So when I configure and compile the vorbis module on my linux box using configure --with-ogg-prefix=/home/warren/local make I get the following error during the make: gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0.0\" -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -I. -I. -I../include -O20 -ffast-math -mno-ieee-fp -D_REENTRANT

This one may be my fault.... I've put a temporary fix for libvorbis not linking, I altered libvorbis_la_LIBADD = to libvorbis_la_LIBADD = $(OGG_LIBS) in the makefile, hence the temporary and continued with the build. I'm now getting gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0.0\" -DHAVE_ALLOCA_H=1 - DHAVE_ALLOCA=1 -I. -I. -I../include

Can I be any more trouble today? :) This almost worked. ./configure worked but when I ran make I got this...a Redhat bug? depmode=gcc /bin/sh ../depcomp \ /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I../include -I. -I../libmp3lame -I.. -O3 -fomit-frame-pointer -ffast-math -funroll-loops -fthread-jumps -malign-double -frerun-loop-opt -fgcse -fexpensive-optimizations

Does anyone know the "standard" commandline to compile and run spec95 benchmarks ? I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not sure if they are the *default ref* configurations. <Some of them seem to use smaller problem sizes.> SPEC95 was retired many years ago, so few people around me know how to compile and run them. I am building from

Hi, This is a repeat question. Earlier I had asked the same question and eventually found the ans. (http://lists.xiph.org/pipermail/vorbis-dev/2005-August/018179.html) However now when I try the same thing somehow I am not able to use debugging. To use debugging, i compiled the source using the folloing commands,. >make clean >./autogen.sh --enable-DEBUG >make The configure.in has

I remember someone saying that compiling flac with gcc 3.0 yields a broken executable. I saw this on the Lame list that might explain the problem. I don't have a gcc 3.0 setup yet but somebody may be able to verify this... --- Alexander Leidinger <Alexander@Leidinger.net> wrote: > From: Alexander Leidinger <Alexander@Leidinger.net> > Subject: Re: [MP3 ENCODER] Lame and

Hi Evan, We did an experiment using the LLVM test suite: we compare the overhead of using our analysis to the LLVM default, both with -O2 option. The overall overhead of compiling the whole test suite using our analysis is 36.5%. The biggest overhead is observed in "SingleSource/Benchmarks/Misc/flops-5", where we are 5 times slower: 0.07s (with our analysis) compared to

On Wed, Oct 23, 2013 at 3:07 AM, Chandler Carruth <chandlerc at google.com> wrote: > On Tue, Oct 22, 2013 at 9:55 AM, Hal Finkel <hfinkel at anl.gov> wrote: >> >> ----- Original Message ----- >> >> It might also be interesting to try with -O3; I don't know if we have any >> significant vectorizable loops in the test suite with a large number of