Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Doug Gregor
For the last few days I've been unable to make or bootstrap on i386-apple-darwin8.10.1. It doesn't seem to be a problem on my Core2-based Mac Pro, but on my Intel Core Duo (MacBook Pro) the build fails with the error message below. Perhaps we're trying to use Core2-only instructions on this platfo

Add a symlink for each branch in online docs

2007-10-02 Thread François-Xavier Coudert
The documentation for different releases of GCC in the same branch vary only slightly. For that reason, I think it would be nice to be able to have a URL for "the doc of a given branch", meaning "the doc of the last released version of this branch". For example, that would be achieved by creating a

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Benjamin Kosnik
>:8390:operands given don't match any known 386 instruction >:8491:operands given don't match any known 386 instruction >make[3]: *** [unwind-dw2_s.o] Error 1 >make[2]: *** [all-stage1-target-libgcc] Error 2 >make[1]: *** [stage1-bubble] Error 2 >make: *** [all] Error 2 You could configure with --

RE: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Jack Howarth
Doug, The fink packaging for gcc42/gcc43 builds fine on Macintel when we use... --with-arch=nocona --with-tune=generic --host=i686-apple-darwin8 to build either gcc 4.2.1 or gcc trunk. Jack

Need help for a net target

2007-10-02 Thread Michael_fogel
Hello For my diploma thesis I have to implement a new back-end for GCC. The microcontroller is based on an FPGA and was developed one year ago. Only an Assembler is available and now my university lecturer wants an C compiler too. I decided to use GCC in version 4.2.1 as basis for the new comp

Re: Need help for a net target

2007-10-02 Thread Andrew Haley
Michael_fogel writes: > Hello > > For my diploma thesis I have to implement a new back-end for GCC. > The microcontroller is based on an FPGA and was developed one year ago. > Only an Assembler is available and now my university lecturer wants an C > compiler too. I decided to use GCC in v