- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting an internal compiler error in one of my modules in Update 6. This is not (as far as I can tell) an unusually complicated module. I have others that are much more complicated -- I'm hesitating..
It seems to be compiling okay in debug mode.
Anyway, is there anyway to track down what it doesn't like in this module? It's a complicated development and will be hard to extract into a project that the premier support people can use.
Linda
It seems to be compiling okay in debug mode.
Anyway, is there anyway to track down what it doesn't like in this module? It's a complicated development and will be hard to extract into a project that the premier support people can use.
Linda
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FYI, I disabled optimization on that particular module and the rest compiled.
Linda
Linda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you supply us that source and the sources for any modules and include files it needs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spent a goodly amount of time trying to create a project that could illustrate, but it compiles that module fine.
Linda
Linda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm going to reply to this thread.
Now have this one compiling if I turn on only "O1" (Minimize Size) option.
But a different module failed when I made a 64 bit EXE last week. (There, too, I just turned off optimization).
I have some other options turned on in my project:
/assume:protect_parens /Qprec-div /Qprec-sqrt /Qimf-precision:high /Qimf-arch-consistency:true
(plus assorted others). Including, now, /fpe3 because we have a c library that seems to need it to not crash on some input files.
Any ideas? Short of giving the entire project to premier support.
Now have this one compiling if I turn on only "O1" (Minimize Size) option.
But a different module failed when I made a 64 bit EXE last week. (There, too, I just turned off optimization).
I have some other options turned on in my project:
/assume:protect_parens /Qprec-div /Qprec-sqrt /Qimf-precision:high /Qimf-arch-consistency:true
(plus assorted others). Including, now, /fpe3 because we have a c library that seems to need it to not crash on some input files.
Any ideas? Short of giving the entire project to premier support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
/fpe3 is the default, so it seems odd you need to use it.
At this point I suggest giving Premier Support the project and let us play with it.
At this point I suggest giving Premier Support the project and let us play with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
/fpe3 is not for this problem -- it's for a library that is part of the project but is written in c and I can't get any developer to play with it. (original developer is not currently available).
was a side comment.
Linda
was a side comment.
Linda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue 646678 posted for this.
Linda
Linda

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