I have run into problems like this before with other compilers.  The
optimizer either has a bug or maybe something in the code should be declared
volatile that is not.  I have generally just backed down the level of
optimization to work around the issue.

If you can isolate the particular file that is the source of the problem,
then you can compile just that file with lower optimization and the segfault
will probably go away.

Anthony

Steven Yi wrote on 2/18/07 9:24 AM:

> I compiled without any gcc4opt flag and things now work!  Strange.  If
> anyone has ideas on why this would be the case I'd love to understand
> what is going on.  Otherwise, I guess I'll continue on with the
> generic optimization build.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net