Yes, this appears to be a known problem, but I can't tell for sure
without a reduced test case of some sort. If you can provide a small
example I can verify whether we've seen this before.
Thanks ...
--Dave
Antoine Pitrou wrote:
Hello,
I'm trying to combine a performance patch based on "labels-as-values" (see
http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html , apparently also supported by sunstudio)
with the IPO options ("-xipo=2 -xipo_archive=writeback") and I'm getting undefined symbol
errors in the linking phase.
I don't have a standalone snippet to reproduce (I could try to make one) but
here is an excerpt of the errors:
Undefined first referenced
symbol in file
$XBBAAA$sbSAN1Fl.PyEval_EvalFrameEx..L223 libpython2.7.a(ceval.o)
$XBBAAA$sbSAN1Fl.PyEval_EvalFrameEx..L224 libpython2.7.a(ceval.o)
$XBBAAA$sbSAN1Fl.PyEval_EvalFrameEx..L225 libpython2.7.a(ceval.o)
[...]
Given the number of symbols, I'm inclined to think that they correspond precisely to the labels
defined using the operator '&&' and then referenced in "goto *xxx" statements.
Is this a known situation? I'm using SunStudio 12.1.1. Things work fine if I
don't activate IPO.
_______________________________________________
tools-compilers mailing list
[email protected]
