- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I'm using Microsoft VisualStudio2005 and Intel C++ Compiler 11.1.061 [IA-32] that comes with theIntel Parallel composer.
When Inavigate through the menu:["Build" -> "Code Coverage Operations" -> "Phase1: Instrument for code coverage"]
The Intel Compiler kicks in and starts compiling the project but breaks with an assert which seems to come from the compiler itself: "shared/pgopti/spi.c:875 ASSERTX(mf_id != -1 && tf_id != -1 && rn_id != -1)"
if i compile the code without instrumenting, everything works fine.
since i'd like to perform code coverage testing and this seems like an Intel Compiler bug, i'd appreciate if someone could help me either work around this problem or further assist you to fix this bug.
Thanks
I'm using Microsoft VisualStudio2005 and Intel C++ Compiler 11.1.061 [IA-32] that comes with theIntel Parallel composer.
When Inavigate through the menu:["Build" -> "Code Coverage Operations" -> "Phase1: Instrument for code coverage"]
The Intel Compiler kicks in and starts compiling the project but breaks with an assert which seems to come from the compiler itself: "shared/pgopti/spi.c:875 ASSERTX(mf_id != -1 && tf_id != -1 && rn_id != -1)"
if i compile the code without instrumenting, everything works fine.
since i'd like to perform code coverage testing and this seems like an Intel Compiler bug, i'd appreciate if someone could help me either work around this problem or further assist you to fix this bug.
Thanks
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There's a known issue related to this error msg that has been fixed. The fix will be available in the 1st Intel Parallel Composer update (releasing around early July if things go well).
Jennifer
Jennifer
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I used the codecov option. It works for me. I am using VS2008 and Intel Parallel Studio.
Could you please help us with the testcase?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There's a known issue related to this error msg that has been fixed. The fix will be available in the 1st Intel Parallel Composer update (releasing around early July if things go well).
Jennifer
Jennifer
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page