- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I turned on the /warn:interface and /gen-interfaces options to check the boundaries between subroutines. The latter of the two causes SOME routines to abort with a "code 1" error. This seems to have nothing at all to do with the contents of the source module. I can't figure out why some routines are affected, but not others.
If I turn off the /gen-interfaces option, they compile but then what do I do if I have to change the argument list?
Is there a way to make these work reliably without jumping thru all these hoops?
What on earth is a code 1 error anyway?
If I turn off the /gen-interfaces option, they compile but then what do I do if I have to change the argument list?
Is there a way to make these work reliably without jumping thru all these hoops?
What on earth is a code 1 error anyway?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you look in the actual build output, you'll see that the compiler died of an internal compiler error. This is always a bug and should be reported to Intel. However, please make sure that you are using the latest compiler (9.1.029 as of this writing), as there have been issues similar to this with the feature you're using and fixes have been made. If you do report the problem, please attach a ZIP of your solution folder with all sources.
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