Hi Amit,
Thanks for the additional insight.  I'm not using the -mlongcall compiler
switch but nonetheless have experieinced CC2.7.2 compiler crashes,
particularly in some of the schema source.

I was able to eliminate some of the compiler crashes by "simplifying" (e.g.
splitting a compound C++ statement containing many operations into multiple
simple C++ statements) the Xerces code fragments that were crashing the
compiler.

Some of the "simplifying" necessary in the schema code proved too laborious
and I resorted to the 

#include <assert.h>

#ifdef VXWORKS
        assert(false);
#else
        XERCES CODE THAT IS CRASHING YOUR COMPILER
#endif

technique since my application doesn't require schema.

- Dennis

-----Original Message-----
From: Shah Amit-ASHAH3 [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 9:57 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Sax Parser on VxWorks


Hello Dennis,

Thanks for the reply. I tried doing that, but only one person answered and
that didnt help much; nothing from the GNU people themselves.
But I discovered the problem late friday evening. And this might be helpful
to others too.

Our build file was using the flag "-mlongcall" alongwith all the other flags
given to ccppc. That was throwing the "unrecognizable insn" error. Though I
dont  exactly know what is meant by "unrecognizable insn", I do know this
has got something to do with jumping between instructions. I just took it
off and it compiled with just some warnings.

I hope atleast some people gain from my experience .. I had already tried 4
versions of Xerces (v1.7, v1.4, v1.3 and v1.2) !!

Thanks,
~Amit



-----Original Message-----
From: Houle, Dennis W [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 11:41 AM
To: [EMAIL PROTECTED]
Subject: RE: Sax Parser on VxWorks


Hi Shah,
Perhaps you could try reposting this to a GNU CC users forum.
- Dennis

-----Original Message-----
From: Shah Amit-ASHAH3 [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 12, 2002 2:35 PM
To: [EMAIL PROTECTED]
Subject: Sax Parser on VxWorks


Hello,

Irrespective of whatever version of Xerces I use, when I try to compile, I
always see the following in the DTD directory. I gather that some people
have used the ccppc compiler before. Has anyone see this earlier? What is
meant by unrecognizable insn? It seems like this is a compiler issue. Can
someone shed some light?

Thanks,
~amit
____________________________________________________________________________
____

ccppc -c -r -Wall -ansi -nostdinc -nostdlib -mlongcall -DRW_MULTI_THREAD
-D_REENTRANT -fvolatile -fno-builtin -fno-defer-pop
-fno-for-scope -DCPU=PPC604 -DVXWORKS -DGOAHEAD  -O1  -I.
-IM:/ashah3_viewSR14880Bld26/hap/vendor/windriver/tornado/nt -IM:/a
shah3_viewSR14880Bld26/hap/vendor/windriver/tornado/nt/target/h
-IM:/ashah3_viewSR14880Bld26/hap/vendor/windriver/tornado/nt/
target/h/sys
-IM:/ashah3_viewSR14880Bld26/hap/vendor/goahead/sr7000/vxworks5.4
-IM:/ashah3_viewSR14880Bld26/hap/vendor/goahea
d/sr7000/vxworks5.4/include
-IM:/ashah3_viewSR14880Bld26/hap/vendor/goahead/sr7000/vxworks5.4/include/sr
k -I../../ DTDValidat
or2.cpp -o 0_build/DTDValidator2.opp


abnormal program termination
In file included from ../../internal/XMLReader.hpp:102,
                 from ../../internal/ReaderMgr.hpp:111,
                 from ../../internal/XMLScanner.hpp:116,
                 from DTDValidator2.cpp:152:
../../framework/XMLRecognizer.hpp:186: warning: `class XMLRecognizer' only
defines a private destructor and has no friends
../../internal/ReaderMgr.hpp: In method
`ThrowEOEJanitor::ThrowEOEJanitor(class ReaderMgr *, bool)':
In file included from ../../internal/XMLScanner.hpp:116,
                 from DTDValidator2.cpp:152:
../../internal/ReaderMgr.hpp:433: warning: member initializers for `bool
ThrowEOEJanitor::fOld'
../../internal/ReaderMgr.hpp:434: warning:   and `class ReaderMgr *
ThrowEOEJanitor::fMgr'
../../internal/ReaderMgr.hpp:412: warning:   will be re-ordered to match
declaration order
../../validators/DTD/DTDValidator.hpp: At top level:
In file included from DTDValidator2.cpp:155:
../../validators/DTD/DTDValidator.hpp:451: warning: `class
NameIdPoolEnumerator<DTDElementDecl>' has virtual functions but no
n-virtual destructor
../../validators/DTD/DTDValidator.hpp:457: warning: `class
NameIdPoolEnumerator<DTDEntityDecl>' has virtual functions but non
-virtual destructor
../../validators/DTD/DTDValidator.hpp:463: warning: `class
NameIdPoolEnumerator<XMLNotationDecl>' has virtual functions but n
on-virtual destructor
DTDValidator2.cpp: In method `class ContentSpecNode *
DTDValidator::scanChildren(const class DTDElementDecl &, class XMLBuffe
r &)':
DTDValidator2.cpp:1119: warning: `enum ContentSpecNode::NodeTypes curType'
might be used uninitialized in this function
DTDValidator2.cpp:1123: warning: `enum ContentSpecNode::NodeTypes type'
might be used uninitialized in this function
DTDValidator2.cpp:1129: warning: `enum ContentSpecNode::NodeTypes type'
might be used uninitialized in this function
DTDValidator2.cpp:1212: warning: `enum ContentSpecNode::NodeTypes type'
might be used uninitialized in this function
DTDValidator2.cpp:1263: warning: `enum ContentSpecNode::NodeTypes type'
might be used uninitialized in this function
DTDValidator2.cpp:1302: internal error--unrecognizable insn:
(call_insn/i 897 896 901 (parallel[
            (call (mem:SI (symbol_ref:SI ("_$_15ContentSpecNode")))
                (const_int 0))
            (use (const_int 0))
            (clobber (scratch:SI))
        ] ) -1 (insn_list 895 (insn_list 896 (nil)))
    (expr_list:REG_DEAD (reg:SI 3 3)
        (expr_list:REG_DEAD (reg:SI 4 4)
            (expr_list:REG_UNUSED (scratch:SI)
                (nil))))
    (expr_list (use (reg:SI 4 4))
        (expr_list (use (reg:SI 3 3))
            (nil))))
DTDValidator2.cpp:1302: confused by earlier errors, bailing out
ccppc: Internal compiler error: program cc1plus got fatal signal 34
*** Error code 1
clearmake: Error: Build script failed for "0_build/DTDValidator2.opp"
"0_build/DTD.out" not remade because of sub-target rebuild errors.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to