------- Comment #32 from jorn dot amundsen at ntnu dot no  2008-09-16 19:09 
-------
(In reply to comment #31)
> No, I do not use any patches from IBM.  The patches seem to be focussed on
> packaging and layout, but I would recommend using the standard FSF GCC 4.3.2
> release plus the pt.c patch that now is upstream in the FSF GCC sources.  We
> cannot help you with a compiler that diverges from the FSF tree.
I will step back to GCC 4.3.2 + pt.c only, leaving out any IBM RPM patches. So
a recompile is on its way. Will take some time.

> Again, I am not sure which versions of GMP and MPFR you are using.  I would
> recommend that you configure and build those packages with --disable-shared 
> and
> ABI=32.
I use gmp 4.2.2 (compiling 4.2.3 just now) and mpfr 2.3.1. Both are compiled as
32- and 64-bit shared libs packaged in one .a-file. I usually compile
everything except 64-bit libs with OBJECT_MODE=32. I doubt gcc even is possible
to build 64-bit.

> You also can try running cc1plus inside GDB and compiling the files to see
> where the ICE occurs.  Right now we cannot reproduce the failures and are
> flying blind.
Yes, I have installed the latest gdb. Also, other GCC applications I've
compiled works just fine in the Etnus Totalview debugger, which we have
installed. However, main focus right now is to step back towards your build
configuration and duplicate your build effort.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37057

Reply via email to