You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Da...@lotus.com on 2001/02/09 21:07:42 UTC
Re: g++ crashes on Solaris for compiling file XMLSupport/FormatterToHTML.cpp
There's nothing wrong with the file, it's a ridiculous limitation of gcc's
optimizer. I've been working on splitting things up for gcc, but I haven't
checked in the changes yet.
For the time being, remove -O from CXXFLAGS the Makefile.
Dave
Wilhelm Vortisch
<wilhelm.vortisch@is To: xalan-dev@xml.apache.org
st.fhg.de> cc: (bcc: David N Bertoni/CAM/Lotus)
Subject: g++ crashes on Solaris for compiling file
02/09/2001 12:19 PM XMLSupport/FormatterToHTML.cpp
Please respond to
xalan-dev
Hi *,
I have no problems to build Xerces-C 1.4.0 with g++ on Solaris 8/SunOS
5.8.
By the compilation of the newest sources (out of CVS) of Xalan there is
a big crash of g++ (with a 80 MB big core - all my quota is gone ...
huhu).
g++ complie the following file:
--------------------------------- snipp
---------------------------------
g++ -O -fPIC -DSOLARIS -instances=static -D_REENTRANT -c -I.
-I/home/wvor/Project/xerces-c-src1_4_0/src/
-I/home/wvor/Project/xerces-c-src1_4_0/include/ -o
/home/wvor/Project/xml-xalan/obj/FormatterToHTML.o
XMLSupport/FormatterToHTML.cpp
g++: Internal compiler error: program cc1plus got fatal signal 11
--------------------------------- snipp
---------------------------------
(The compiler option -DXALAN_NO_NAMESPACE didn't make any difference
...)
On a linux system I have no problems ....
What's wrong with this file??
Any tips&help are welcome ...
CU
Wilhelm
--
Fraunhofer ISST | Telefon : +49 (0) 30/2 43 06-4 22
Bereich ITM | Telefax : +49 (0) 30/2 43 06-1 99
Mollstr. 1 | E-Mail : Wilhelm.Vortisch@isst.fhg.de
D-10178 Berlin | Internet : http://www.isst.fhg.de
Xalan C++, How does the node indexing work?
Posted by David Braaten <da...@multiactive.com>.
The XalanSourceTree introduced node-order indexing, but I haven't seen
node-order indexing before.
Is it as simple as: For a given Parent Node, the child returned by
getFirstChild would return a node with an index of 0 and calling
getNextSibling would
return a node with an index of 1, etc... ?
A short explanation would be much appreciated ;)
tia
-Dave