Shark and icpc
Shark and icpc
- Subject: Shark and icpc
- From: kwiley <email@hidden>
- Date: Thu, 21 Aug 2008 11:29:15 -0700
I'm trying to profile an executable compiled with icpc, not g++. The
actual optimizations performed for each standard optimization level
(1, 2, 3) seem to differ slightly between the two compilers, but I
didn't except any really dramatic differences. However, Shark has a
lot of trouble with icpc generated code. Shark handles g++ -O1 code
pretty well, although things get harder past -O1. With icpc -O1 code,
Shark produces very strange output. I am not only referring to the
"source view". I understand that source code should be difficult to
interpret with high levels of optimization. I am referring to the
default tree view. With icpc -O1, the tree view is a complete mess.
There is effectively no tree view at all. There is next to no
hierarchical nesting of function calls for example. As a matter of
fact, start() and main() aren't even shown! Notice that with icpc
generated code with no optimizations at all, Shark works as usual, so
it is at least basically compatible (which I would expect since the
various debugging meta-info standards shouldn't differ between g++ and
icpc), but with -O1 it just falls over.
Does anyone have any ideas about this: either what's going on, or what
might be done about it?
Thanks.
________________________________________________________________________
Keith Wiley email@hidden http://www.cs.unm.edu/~kwiley
"I used to be with it, but then they changed what it was. Now, what I'm
with isn't it, and what's it seems weird and scary to me."
-- Abe (Grandpa) Simpson
________________________________________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden