Full_Name: MJ Ray Version: 0.99.0a OS: Linux 2.2.13 Slackware 7.0 Submission from: (NULL) (195.7.239.50) I consistently get a sig11 on one file: gcc -I. -I../include -I../../src/include -I../../src/include/R_ext -DHAVE_CONFIG_H -mieee-fp -g -O2 -c fft.c -o fft.o gcc: Internal compiler error: program cc1 got fatal signal 11 make[3]: *** [fft.o] Error 1 However, other files and parts of the tree compile still. (When I had a sig11 being caused by a memory fault, once it sig11'd, it would sig11 again.) I can even do a successful kernel compile. Just not that one file. I tried removing the ^L from the file with no effect. I'm stumped and am grabbing the latest devel tarball to see if that does the same. -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
h089@mth.uea.ac.uk writes:> I consistently get a sig11 on one file: > > gcc -I. -I../include -I../../src/include -I../../src/include/R_ext > -DHAVE_CONFIG_H -mieee-fp -g -O2 -c fft.c -o fft.o > gcc: Internal compiler error: program cc1 got fatal signal 11 > make[3]: *** [fft.o] Error 1 > > However, other files and parts of the tree compile still. (When I had a sig11 > being > caused by a memory fault, once it sig11'd, it would sig11 again.) I can evenC compilers can do that all by themselves occasionally. Which version are we talking about? Does it work to change the optimisation level for the file? -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics 2200 Cph. N (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk) FAX: (+45) 35327907 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
On Sat, Feb 12, 2000 at 12:36:57AM +0100, Peter Dalgaard BSA wrote:> h089@mth.uea.ac.uk writes: > > I consistently get a sig11 on one file: > > gcc -I. -I../include -I../../src/include -I../../src/include/R_ext > > -DHAVE_CONFIG_H -mieee-fp -g -O2 -c fft.c -o fft.o > > gcc: Internal compiler error: program cc1 got fatal signal 11 > > make[3]: *** [fft.o] Error 1 > C compilers can do that all by themselves occasionally. Which version > are we talking about? Does it work to change the optimisation level > for the file?markj@oplex$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Reducing the optimisation to O1 compiles it, but O3 still does the sig11. Thanks. Problem cured if not explained. MJR -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._