I guess I didn't make myself clear. Can you please explain your
example in more detail? The original one, not traces. I don't fully
understand your example.
Sun
On Tue, Feb 8, 2011 at 3:23 AM, Feng Zhou wrote:
> Sun,
>
> For bug #707, the symptom is compile-time assertion:
> ### Assertion failure
I think you are in the wrong track. I'd like to know the symbol
attribute of the string that became part of the erronous code. The bug
is not in IPA, nor the CPIC/PIC flag themselves. Those are concepts
that, if turned off, of course a lot of things will start working,
because you basically turned
Sun,
Based on your email, I changed my fix to the following (also as attachment):
Index: osprey/common/com/config.cxx
===
--- osprey/common/com/config.cxx(revision 3471)
+++ osprey/common/com/config.cxx(working copy)
Sun,
For bug #707, the symptom is compile-time assertion:
### Assertion failure at line 921 of
/wsp/fzhou/open64/dbg-objdir/osprey/../../open64/osprey/be/opt/opt_verify.cxx:
### Compiler Error in file test.c during Global Optimization -- Verify
Live-Range phase:
### sym8v2(cr13) live range overlap
