Intel Visual Fortran Error Message
in [Fortran]
|
Prev: printing output in fortran without preceding white space
Next: Buy Tramadol fedex without prescription, Tramadol shipped overnight no prescription
From: rfengineer55 on 27 Jun 2010 18:28 On Jun 27, 3:58 pm, Steve Lionel <steve.lio...(a)intel.invalid> wrote: > On 6/27/2010 2:17 PM, rfengineer55 wrote: > > > > > I think you're right on. Given your observations and suggestions, I'm > > going to do some digging in the VS 2008 and find out more about the > > Class references that I briefly noted. Hopefully there will be an easy > > fix. I I can convince the compiler to treat class1 as written rather > > than parsing it as class 1 like you're saying, I should be good to go. > > Jeff, > > Please make sure you are using the current Intel compiler, 11.1.065 > (Update 6). An older version did have some issues with declarations of > variables whose names started with CLASS. You should not have to do > anything to get this accepted - we fixed the bug several months ago. > > If you find you are still having these errors with 11.1.065, let me know. > > -- > Steve Lionel > Developer Products Division > Intel Corporation > Nashua, NH > > For email address, replace "invalid" with "com" > > User communities for Intel Software Development Products > http://software.intel.com/en-us/forums/ > Intel Software Development Products Support > http://software.intel.com/sites/support/ > My Fortran blog > http://www.intel.com/software/drfortran Steve, I do not see a Help -> About in VS 2008 where I can check the version number. What is the name of the executable, and I'll go into windows and pull up the Properties of the file and check that out. I bought this software a little less than a month ago through CDW using an Academic discount. The exact date of purchase is probably in your records. Also, please send along an email address where I can write to you directly. I used the Reply to Autor button here, and got no response from you. Perhaps you have email sen by that feature blocked out. My compiler will die in a couple weeks, and the info I received from a support specialist at Intel was not valid information. I really rather not say much more than that in a public forum. Steve, thank you for your help with this immediate issue, and I hope you can help me keep my compiler running. Jeff RF ENGINEER55
From: Louis Krupp on 27 Jun 2010 18:40 On 6/27/2010 4:20 PM, rfengineer55 wrote: <snip> > These class2, class3, class4 and class_out variable names are mission > critical, so if there was a fortran declaration or logic error with > those, the entire program would be a failure. <snip> Have you written and tried to compile a small test program that uses these variables? That could help you narrow things down a bit. Louis
From: rfengineer55 on 27 Jun 2010 18:41 On Jun 27, 3:58 pm, Steve Lionel <steve.lio...(a)intel.invalid> wrote: > On 6/27/2010 2:17 PM, rfengineer55 wrote: > > > > > I think you're right on. Given your observations and suggestions, I'm > > going to do some digging in the VS 2008 and find out more about the > > Class references that I briefly noted. Hopefully there will be an easy > > fix. I I can convince the compiler to treat class1 as written rather > > than parsing it as class 1 like you're saying, I should be good to go. > > Jeff, > > Please make sure you are using the current Intel compiler, 11.1.065 > (Update 6). An older version did have some issues with declarations of > variables whose names started with CLASS. You should not have to do > anything to get this accepted - we fixed the bug several months ago. > > If you find you are still having these errors with 11.1.065, let me know. > > -- > Steve Lionel > Developer Products Division > Intel Corporation > Nashua, NH > > For email address, replace "invalid" with "com" > > User communities for Intel Software Development Products > http://software.intel.com/en-us/forums/ > Intel Software Development Products Support > http://software.intel.com/sites/support/ > My Fortran blog > http://www.intel.com/software/drfortran Steve, OK, I found it. Did not realize at first that the Intel ver could not be harvested via Visual Studio 2008. My Programs shortcut under Software Development Tools says Compiler rofessional 11.1.048, so it would appear thyat I have an old version then. When I bought this software, it came on a CDR as opposed to a download. I hope this information helps. Thanks, Jeff
From: Richard Maine on 27 Jun 2010 18:57 rfengineer55 <rfengineer55(a)aol.com> wrote: > If you can pass along an email address, I can email you the source > code. As with Steve, my email address is in my signature. However, I don't do private consulting. I post my address for people who might have personal reason to email me. "Personal reason" does not include Fortran debugging except in most unusual situations (which don't come close to applying here). P.S. Note Steve's separate comment about what sounds like a plausibly related compiler bug. If that is the problem, which seems plausible given Steve's comments, I wouldn't be able to do much about it anyway. -- Richard Maine | Good judgment comes from experience; email: last name at domain . net | experience comes from bad judgment. domain: summertriangle | -- Mark Twain
From: dpb on 28 Jun 2010 09:05
rfengineer55 wrote: .... > I don'tknow where the problem is, so it's difficult to know where the > snip point should be. I can post the entire source here if you want; I > have no objection. .... Generally, unless as Louis suggests you make a small test program--almost always a most excellent diagnostic tool, as noted, btw--the entire source is generally too much information for usenet. Granted, learning how to selectively decide what is significant does take some effort. It's a generic problem that doesn't afflict only you -- but in particular, it's essentially impossible to say anything useful about variables and/or functions without the associated declarations as a bare minimum. Similarly, if the issue has to do w/ a calling sequence or variable association or indexing in subprograms, unless one has the declarations in both the caller and callee it's not possible in general to find mismatches or difficulties there. Also, it is much better to cut and paste without interpretation directly from the compiler output and the source files than to try to paraphrase or recreate. Subtle changes in wordings of error messages or typos can inadvertently lead in the wrong path(s) or introduce other issues as in the first posting despite the intent to be both concise and helpful. I see later on that Steve L pointed out that there was indeed a parsing error in an earlier release of the IVF compiler; I thought of that as a possibility and almost suggested you go look at the Intel site and see if there were any updates but knowing it was recent acquisition had presumed that had been done. Which teaches a lesson on the other end--one shouldn't presume... :) Anyway, I gather that resolved the issue... -- |