- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is an update regarding the progress Intel?s Software Products Division is making with Intel Visual Fortran for Windows*.
In March, 2002, Intel outlined intermediate and longer term plans to produce Intel Fortran products to which Visual Fortran users can move without disrupting their development efforts. At that time, Intel committed to deliver an update to Intel Fortran that included improved compatibility with Compaq Visual Fortran in the Q4?02 to Q1?03 timeframe.
Intel Fortran 7.0, introduced in December 2002, delivered on this commitment. The 7.0 release provided many features familiar to Visual Fortran users including command line options, auxiliary libraries, Array Visualizer technology, and integration into Microsoft Visual Studio*.NET. Intel further enhanced this offering with the Intel Fortran 7.1 release, which was made available in March, 2003. Like previous Intel compilers, each license includes the right to use the compiler on systems using IA-32 processors, such as the new Pentium M processor, and Itanium processors, such as the Itanium 2 processor.
Intel also outlined its longer term intention to move from the current Intel Fortran front-end (provides Fortran language features) to the Visual Fortran front-end. This remains Intel?s vision for Fortran and Intel intends to deliver this compiler in Q4 of 2003 (the timeframe from the earlier status report was noted as the 2nd half of 2003). At that time, Intel expects to rename the product to Intel Visual Fortran.
Intel expects to offer Intel Visual Fortran as a compiler that integrates into the Microsoft* Visual C++ .NET 2002 or 2003 (MSVC++) development environment, but we do not intend to include the Microsoft environment with the compiler. Our plan is to offer Intel Visual Fortran so users will not need to buy anything additional if they already have MSVC++ .NET 2002 or 2003 in Microsoft Visual Studio .NET 2002 or 2003 or through a subscription to MSDN. We also intend to work with resellers interested in selling bundled forms of MSVC++ .NET 2002 or 2003 with Intel Visual Fortran, so that everything customers need can be purchased from one company in one transaction.
The basis for this decision is multifaceted. Differences between Microsoft and Intel customer licensing and support models were major factors. In addition, the market has changed since Digital* Visual Fortran* first appeared. Today, most Windows based developers already have the Microsoft Visual C++ development environment in forms such as Visual C++*, Visual Studio itself or via MSDN*. Some customers commented that another distribution of this popular environment was not necessary and others commented they preferred to keep their IDEs consistent for support purposes.
Intel intends to offer a ?Standard? and ?Professional? version of Intel Visual Fortran. The standard version is planned to include all of the features currently available in the Intel Fortran product, including the Array Visualizer technology, plus additional compatibility with Compaq Visual Fortran. The Professional version is planned to contain the same compiler plus Visual Numerics? IMSL* Fortran Numerical Library 5.0 for both IA-32 and Itanium architecture-based systems. Pricing for the Standard and Professional versions has not yet been determined.
Intel intends to sell the IMSL Fortran Library under single user developer license terms specified by Visual Numerics, Inc., the provider of the library. Visual Numerics? end-user license terms will allow for single developer use of IMSL in conjunction with single-user licenses of Intel Fortran. In addition, a no-cost license for deployment of applications including IMSL will be included. Visual Numerics? development and deployment end user licenses available through Intel will apply to systems of four or fewer processors and non-cluster environments. For different configurations, Visual Numerics intends to offer licenses directly to end-users. For more information concerning IMSL Fortran Numerical Library 5.0, please contact Visual Numerics directly through their web site at http://www.vni.com/ .
Intel intends to offer direct customer support for Intel Visual Fortran and the IMSL Fortran Library through Intel Premier Support. For more information on support, see the attached set of questions and answers.
Intel is making every effort to provide a smooth transition path to Intel Visual Fortran. It is our goal to deliver exceptional compiler technology that will be an attractive upgrade to Compaq Visual Fortran.
The Intel Compiler team works as part of the larger Intel Software Products Division to provide software development products that take best advantage of the Intel Architecture, including Pentium 4 and Itanium processors. Intel already offers Fortran compilers for both Windows and Linux as each runs on IA-32 and Itanium architecture-based processors. Fortran developers who want to exploit the performance potential of the Intel Architecture in these operating environments can begin using Intel compilers today.
Intel is dedicated to providing the best software development tools for developers interested in taking advantage of the Intel Architecture. The Intel product line includes Intel Fortran and Intel C++ Compilers, VTune? Performance Analyzer, Intel Performance Libraries, tools for the development and maintenance of threaded software in the Intel Thread Checker and training from the Intel Software College. Intel offers the earliest, easiest and fastest access to tools that deliver the performance of the Intel Architecture. Intel provides performance-oriented tools that are compatible with the way software developers work and we back them up with our acclaimed Premier Support.
For more information on the Intel software development product line, including evaluation copies, visit http://www.intel/com/software/products .
All information provided related to future Intel products and plans is preliminary and subject to change at any time, without notice.
*Other names and brands may be claimed as the property of others.
Intel, Pentium, Itanium and VTune are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Questions and Answers regarding Intel Fortran plans (July, 2003)
Q1. When will Intel Fortran for Windows replace Compaq* Visual Fortran*?
A1. Intel cannot speak to HP plans for CVF but Intel intends to offer Intel Visual Fortran as an upgrade for both Compaq Visual Fortran and Intel Fortran. This is expected to be available in Q4 2003.
Q2. How will I get support for CVF after Intel Visual Fortran is released?
A2. Support for CVF is provided by HP via the vf-support@compaq.com e-mail address. Intel cannot speak for HP but it is our expectation that t echnical support will be available for a limited time after the release of Intel Visual Fortran.
Q3. Will Intel Fortran include an Integrated Development Environment (IDE)?
A3. No. Differences between Microsoft and Intel regarding customer licensing and support models were major factors in this decision. In addition, the market has changed since IDE-based Fortran products first appeared. Today, most Windows based developers already have Visual Studio in forms such as Visual C++*, Visual Studio itself or via MSDN*. Some customers commented that another distribution of this popular environment was not necessary and others commented they preferred to keep their IDEs consistent for support purposes.
Q4. What should customers do who want an IDE?
A4. Intel intends to work with Microsoft to make it easy for customers to purchase Microsoft Visual Studio or Visual C++ from their preferred reseller or directly from Microsoft.
Q5. Is Microsoft Visual C++ .NET 2002 or 2003 or Visual Studio .NET 2002 or 2003 a requirement for Intel Fortran?
A5. It is Intel?s intention to require Microsoft Visual C++ .NET 2002 or 2003 or Visual Studio .NET 2002 or 2003 in order to successfully build applications.
Q6. Will there be a command-line version of Intel Fortran for Windows?
A6. The compiler can be used from a command line but Microsoft Visual C++.NET or Visual Studio.Net will need to be installed.
Q7. Will Intel offer ?Standard? and ?Professional? packaging of Intel Visual Fortran?
A7. It is Intel?s intention to sell a Standard and Profession edition of Intel Fortran. We may include Array Visualizer technology in the Standard package, much as we do currently with Intel Fortran 7.1. The major addition to the Professional version will be the IMSL Fortran Numerical Library 5.0.
Q8. How much will the compiler cost ? both the Standard and Professional edition?
A8. Pricing has not been set but Intel intends to offer competitive pricing
Q9. Will there be upgrade pricing?
A9. Again, pricing has not been set but Intel intends to offer competitive pricing.
Q10. What are the higher-level points of the license terms?
A10. Intel software development products are licensed on a subscription basis. That is, you purchase a license and you get a product, support and all updates ? including major and minor releases ? for one year. Licenses include the rights to use the Intel Fortran compiler on both IA32 and Itanium systems. Customers must register with Intel Premier Support to take advantage of the support and update features of their license. At the end of a year, customers can renew their subscription or not. If they choose not to, they can continue to use the last compiler they got during their year of support services but they will not be eligible for ongoing customers support services, including updates and issue-resolution. You can think of it as a magazine subscription: You subscribe and get new magazines every so often. You can keep the publications and read them again and again. If you choose not to renew your subscription, you can continue to read the old editions but you won?t get any new ones.
Q11. Where can I get more information?
A11. You can go to the Intel Software Development Products web page from time to time: http://www.intel.com/software/products. Intel sponsors forums on Intel Fortran and Intel C++ for developers interested in con versing about a wide variety of topics. Feel free to join in. You can start a topic of interest to you (tell us your requirements!) or join in an existing discussion. From the web page, scroll down the left margin to the User Community link, ?mouse-over? the link or click it, and select the forum of choice.
In March, 2002, Intel outlined intermediate and longer term plans to produce Intel Fortran products to which Visual Fortran users can move without disrupting their development efforts. At that time, Intel committed to deliver an update to Intel Fortran that included improved compatibility with Compaq Visual Fortran in the Q4?02 to Q1?03 timeframe.
Intel Fortran 7.0, introduced in December 2002, delivered on this commitment. The 7.0 release provided many features familiar to Visual Fortran users including command line options, auxiliary libraries, Array Visualizer technology, and integration into Microsoft Visual Studio*.NET. Intel further enhanced this offering with the Intel Fortran 7.1 release, which was made available in March, 2003. Like previous Intel compilers, each license includes the right to use the compiler on systems using IA-32 processors, such as the new Pentium M processor, and Itanium processors, such as the Itanium 2 processor.
Intel also outlined its longer term intention to move from the current Intel Fortran front-end (provides Fortran language features) to the Visual Fortran front-end. This remains Intel?s vision for Fortran and Intel intends to deliver this compiler in Q4 of 2003 (the timeframe from the earlier status report was noted as the 2nd half of 2003). At that time, Intel expects to rename the product to Intel Visual Fortran.
Intel expects to offer Intel Visual Fortran as a compiler that integrates into the Microsoft* Visual C++ .NET 2002 or 2003 (MSVC++) development environment, but we do not intend to include the Microsoft environment with the compiler. Our plan is to offer Intel Visual Fortran so users will not need to buy anything additional if they already have MSVC++ .NET 2002 or 2003 in Microsoft Visual Studio .NET 2002 or 2003 or through a subscription to MSDN. We also intend to work with resellers interested in selling bundled forms of MSVC++ .NET 2002 or 2003 with Intel Visual Fortran, so that everything customers need can be purchased from one company in one transaction.
The basis for this decision is multifaceted. Differences between Microsoft and Intel customer licensing and support models were major factors. In addition, the market has changed since Digital* Visual Fortran* first appeared. Today, most Windows based developers already have the Microsoft Visual C++ development environment in forms such as Visual C++*, Visual Studio itself or via MSDN*. Some customers commented that another distribution of this popular environment was not necessary and others commented they preferred to keep their IDEs consistent for support purposes.
Intel intends to offer a ?Standard? and ?Professional? version of Intel Visual Fortran. The standard version is planned to include all of the features currently available in the Intel Fortran product, including the Array Visualizer technology, plus additional compatibility with Compaq Visual Fortran. The Professional version is planned to contain the same compiler plus Visual Numerics? IMSL* Fortran Numerical Library 5.0 for both IA-32 and Itanium architecture-based systems. Pricing for the Standard and Professional versions has not yet been determined.
Intel intends to sell the IMSL Fortran Library under single user developer license terms specified by Visual Numerics, Inc., the provider of the library. Visual Numerics? end-user license terms will allow for single developer use of IMSL in conjunction with single-user licenses of Intel Fortran. In addition, a no-cost license for deployment of applications including IMSL will be included. Visual Numerics? development and deployment end user licenses available through Intel will apply to systems of four or fewer processors and non-cluster environments. For different configurations, Visual Numerics intends to offer licenses directly to end-users. For more information concerning IMSL Fortran Numerical Library 5.0, please contact Visual Numerics directly through their web site at http://www.vni.com/ .
Intel intends to offer direct customer support for Intel Visual Fortran and the IMSL Fortran Library through Intel Premier Support. For more information on support, see the attached set of questions and answers.
Intel is making every effort to provide a smooth transition path to Intel Visual Fortran. It is our goal to deliver exceptional compiler technology that will be an attractive upgrade to Compaq Visual Fortran.
The Intel Compiler team works as part of the larger Intel Software Products Division to provide software development products that take best advantage of the Intel Architecture, including Pentium 4 and Itanium processors. Intel already offers Fortran compilers for both Windows and Linux as each runs on IA-32 and Itanium architecture-based processors. Fortran developers who want to exploit the performance potential of the Intel Architecture in these operating environments can begin using Intel compilers today.
Intel is dedicated to providing the best software development tools for developers interested in taking advantage of the Intel Architecture. The Intel product line includes Intel Fortran and Intel C++ Compilers, VTune? Performance Analyzer, Intel Performance Libraries, tools for the development and maintenance of threaded software in the Intel Thread Checker and training from the Intel Software College. Intel offers the earliest, easiest and fastest access to tools that deliver the performance of the Intel Architecture. Intel provides performance-oriented tools that are compatible with the way software developers work and we back them up with our acclaimed Premier Support.
For more information on the Intel software development product line, including evaluation copies, visit http://www.intel/com/software/products .
All information provided related to future Intel products and plans is preliminary and subject to change at any time, without notice.
*Other names and brands may be claimed as the property of others.
Intel, Pentium, Itanium and VTune are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Questions and Answers regarding Intel Fortran plans (July, 2003)
Q1. When will Intel Fortran for Windows replace Compaq* Visual Fortran*?
A1. Intel cannot speak to HP plans for CVF but Intel intends to offer Intel Visual Fortran as an upgrade for both Compaq Visual Fortran and Intel Fortran. This is expected to be available in Q4 2003.
Q2. How will I get support for CVF after Intel Visual Fortran is released?
A2. Support for CVF is provided by HP via the vf-support@compaq.com e-mail address. Intel cannot speak for HP but it is our expectation that t echnical support will be available for a limited time after the release of Intel Visual Fortran.
Q3. Will Intel Fortran include an Integrated Development Environment (IDE)?
A3. No. Differences between Microsoft and Intel regarding customer licensing and support models were major factors in this decision. In addition, the market has changed since IDE-based Fortran products first appeared. Today, most Windows based developers already have Visual Studio in forms such as Visual C++*, Visual Studio itself or via MSDN*. Some customers commented that another distribution of this popular environment was not necessary and others commented they preferred to keep their IDEs consistent for support purposes.
Q4. What should customers do who want an IDE?
A4. Intel intends to work with Microsoft to make it easy for customers to purchase Microsoft Visual Studio or Visual C++ from their preferred reseller or directly from Microsoft.
Q5. Is Microsoft Visual C++ .NET 2002 or 2003 or Visual Studio .NET 2002 or 2003 a requirement for Intel Fortran?
A5. It is Intel?s intention to require Microsoft Visual C++ .NET 2002 or 2003 or Visual Studio .NET 2002 or 2003 in order to successfully build applications.
Q6. Will there be a command-line version of Intel Fortran for Windows?
A6. The compiler can be used from a command line but Microsoft Visual C++.NET or Visual Studio.Net will need to be installed.
Q7. Will Intel offer ?Standard? and ?Professional? packaging of Intel Visual Fortran?
A7. It is Intel?s intention to sell a Standard and Profession edition of Intel Fortran. We may include Array Visualizer technology in the Standard package, much as we do currently with Intel Fortran 7.1. The major addition to the Professional version will be the IMSL Fortran Numerical Library 5.0.
Q8. How much will the compiler cost ? both the Standard and Professional edition?
A8. Pricing has not been set but Intel intends to offer competitive pricing
Q9. Will there be upgrade pricing?
A9. Again, pricing has not been set but Intel intends to offer competitive pricing.
Q10. What are the higher-level points of the license terms?
A10. Intel software development products are licensed on a subscription basis. That is, you purchase a license and you get a product, support and all updates ? including major and minor releases ? for one year. Licenses include the rights to use the Intel Fortran compiler on both IA32 and Itanium systems. Customers must register with Intel Premier Support to take advantage of the support and update features of their license. At the end of a year, customers can renew their subscription or not. If they choose not to, they can continue to use the last compiler they got during their year of support services but they will not be eligible for ongoing customers support services, including updates and issue-resolution. You can think of it as a magazine subscription: You subscribe and get new magazines every so often. You can keep the publications and read them again and again. If you choose not to renew your subscription, you can continue to read the old editions but you won?t get any new ones.
Q11. Where can I get more information?
A11. You can go to the Intel Software Development Products web page from time to time: http://www.intel.com/software/products. Intel sponsors forums on Intel Fortran and Intel C++ for developers interested in con versing about a wide variety of topics. Feel free to join in. You can start a topic of interest to you (tell us your requirements!) or join in an existing discussion. From the web page, scroll down the left margin to the User Community link, ?mouse-over? the link or click it, and select the forum of choice.
Link Copied
30 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The above message is an official communication from Intel, which means it passed through lots of hands (including lawyers!) I helped with it, but did not write most of it. If you have additional questions, feel free to ask here and I'll do my best.
One thing I realize the above doesn't say is that the minimum prerequsite will be Microsoft Visual C++.NET Standard Edition, which typically sells for under $100. Pricing of Intel Visual Fortran is planned to be such that if you need to buy both it and MSVC++ Standard, you'll still be paying less than Compaq charged for CVF - substantially less in some cases.
Steve
One thing I realize the above doesn't say is that the minimum prerequsite will be Microsoft Visual C++.NET Standard Edition, which typically sells for under $100. Pricing of Intel Visual Fortran is planned to be such that if you need to buy both it and MSVC++ Standard, you'll still be paying less than Compaq charged for CVF - substantially less in some cases.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
1. Could you comment on the extent to which IVF will duplicate CVF's support for direct-Fortran access to Win32 APIs? Will IVF include a set of INTERFACE and definition modules similar (or more inclusive than) those provided with CVF? Will it still be possible to build all-Fortran native Win32 apps?
2. Has any progress been made in addressing the "compilation cascade" problem for multi-module projects? Does the .NET IDE fix the dependency-checker problems of the old VS IDE?
1. Could you comment on the extent to which IVF will duplicate CVF's support for direct-Fortran access to Win32 APIs? Will IVF include a set of INTERFACE and definition modules similar (or more inclusive than) those provided with CVF? Will it still be possible to build all-Fortran native Win32 apps?
2. Has any progress been made in addressing the "compilation cascade" problem for multi-module projects? Does the .NET IDE fix the dependency-checker problems of the old VS IDE?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. Yes, Win32 API support will be there at least at the level of CVF 6.6.
2. The compilation dependency analyzer is different under VS.NET and should be better than CVF's. I haven't seen a problem in my own use.
Steve
2. The compilation dependency analyzer is different under VS.NET and should be better than CVF's. I haven't seen a problem in my own use.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The visual c++ .net requirement will keep us
away from it for now. We can't use anything with
.net in it until it gets passed by our internal
architectural review, which can take a while.
away from it for now. We can't use anything with
.net in it until it gets passed by our internal
architectural review, which can take a while.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is it about VC++.NET that is the problem? Would it be ok if this was called VC++7?
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I suspect so. This is in the environment of a very
large utility company, and the powers-that-be are understandably conservative about unleashing new technology into the infrastructure. .net technology is 'contained' until a pilot study is completed.
large utility company, and the powers-that-be are understandably conservative about unleashing new technology into the infrastructure. .net technology is 'contained' until a pilot study is completed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You would not be using ".NET" technology with Intel Fortran (though VC++.NET is capable of it.)
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's the rub. Even if the Fortran doesn't use it,
the capability is there, so I can't have it.
the capability is there, so I can't have it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't know if I dreamt this or not, but did you recently say that _all_ features in CVF 6.6B(C) will be supported in IVF? Hope I got this right as I like CVF. The announcement doesn't mention the free upgrade for IFC 7.1 registered users with active suscriptions at the time of IVF's release. Is that still on?
Ciao,
Gerry T.
Ciao,
Gerry T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Could you please comment more on the Integrated Development Environment(s). My knowledge of .NET is limited to the spelling. Does this mean the current visual environment of my existing CVF 6.6B will no longer work with IVF? Will I be required to learn a completely new application? Are the editing tools/macros/keyboard shortcuts different?
If different, can both applications be run independently?
Thanks,
Greg
Could you please comment more on the Integrated Development Environment(s). My knowledge of .NET is limited to the spelling. Does this mean the current visual environment of my existing CVF 6.6B will no longer work with IVF? Will I be required to learn a completely new application? Are the editing tools/macros/keyboard shortcuts different?
If different, can both applications be run independently?
Thanks,
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since this thread now seems to encompass IDE issues, I would appreciate further specific remarks on the F90 "compilation cascade," which has been much discussed -- but certainly not solved -- here before.
The issue is that any change to any source file, however trivial and however unrelated to issues of interface structure and parameter passing, always results in the ENTIRE PROJECT being recompiled before linking. So what ought to be a 15-second turnaround for a simple code tweak actually takes 15 minutes for a large multi-module project.
This is always blamed on problems with Microsoft's IDE dependency checker, and thus not directly the fault of the compiler developer. But these problems are very real, and result in uncounted expensive wasted hours. I would love to either see this fixed, or, failing that, have a means to TURN IT OFF, so I can compile manually and (re)link whatever generation of OBJ/MODs are present, without any second-guessing by the IDE. I would willingly pay BIG MONEY if IVF solves this one (and, conversely, I will feel very ripped off if you haven't).
The issue is that any change to any source file, however trivial and however unrelated to issues of interface structure and parameter passing, always results in the ENTIRE PROJECT being recompiled before linking. So what ought to be a 15-second turnaround for a simple code tweak actually takes 15 minutes for a large multi-module project.
This is always blamed on problems with Microsoft's IDE dependency checker, and thus not directly the fault of the compiler developer. But these problems are very real, and result in uncounted expensive wasted hours. I would love to either see this fixed, or, failing that, have a means to TURN IT OFF, so I can compile manually and (re)link whatever generation of OBJ/MODs are present, without any second-guessing by the IDE. I would willingly pay BIG MONEY if IVF solves this one (and, conversely, I will feel very ripped off if you haven't).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Let's see what I can say here...
Intel Visual Fortran will support all Fortran language features and extensions that CVF 6.6B supports. If there are exceptions to this, I'm not aware of them. There will be some overall CVF product features that won't be supported in the first release - CXML is one that comes to mind, as is the MS profiler, which MS has dropped. Intel has alternatives for these, though they need to be purchased separately.
The goal is "rebuild and go", which most users should see. The exceptions will be those who depend on CVF defaults for calling mechanisms, as the default is being switched to the C mechanism (still reference passing), which is consistent with just about every other compiler out there. While STDCALL has its advantages, and is what MS PowerStation used, I think this is the right decision. We did not come to this lightly, I can assure you.
The IDE is different, though more in appearance than in actual use. Personally, I prefer the MS V6 IDE, but MS didn't ask my opinion... Mixed Fortran-C projects will be more complicated - VS.NET doesn't allow for multiple language sources in a project, but you can build a "Solution" (sort of a master project - the concept doesn't appear in VS6) which contains projects from different languages and links them together.
I believe that the compilation cascade issue is not in the new IDE, as the dependence analyzer is now all our own code (I think).
You can have CVF and Intel Visual Fortran on the same system, and they will each operate on their own. My own system has CVF/Visual Studio 6, Visual Studio.NET 2002 and 2003, with Intel Fortran and C++ integrated into the latter.
If you purchased Intel Fortran already, you get 12 months of support with free upgrades. That hasn't changed and I know of no plans to change it. After the year, you can renew for another year - the current price for that is $200. Intel uses the support subscription model which is different from the way CVF did things. Some customers will like this, some won't. Some didn't like the CVF way either. C'est la vie...
I expect the upgrade from CVF to Intel Visual Fortran to be the same $200. Note that Intel Visual Fortran will include Array Visualizer, which was only in the CVF Pro edition. IMSL will be available as an extra cost option, but it will not be anywhere near as cheap as it was with CVF. Visual Numerics has changed their pricing structure and we have to accomodate.
Support is handled differently, and better in many ways. Instead of an e-mail address, there's a web site (https://premier.intel.com/) where you enter your support request and can attach files, all in a secure environment. What's nice about this is that you can track the status of all your support requests, and get updated files all from within your web browser. The support team (of which I'm now a member) is very good and dedicated. You won't be always dealing with me directly, but I'll be there making sure you get the best possible support.
I think that's enough for tonight!
Steve
Intel Visual Fortran will support all Fortran language features and extensions that CVF 6.6B supports. If there are exceptions to this, I'm not aware of them. There will be some overall CVF product features that won't be supported in the first release - CXML is one that comes to mind, as is the MS profiler, which MS has dropped. Intel has alternatives for these, though they need to be purchased separately.
The goal is "rebuild and go", which most users should see. The exceptions will be those who depend on CVF defaults for calling mechanisms, as the default is being switched to the C mechanism (still reference passing), which is consistent with just about every other compiler out there. While STDCALL has its advantages, and is what MS PowerStation used, I think this is the right decision. We did not come to this lightly, I can assure you.
The IDE is different, though more in appearance than in actual use. Personally, I prefer the MS V6 IDE, but MS didn't ask my opinion... Mixed Fortran-C projects will be more complicated - VS.NET doesn't allow for multiple language sources in a project, but you can build a "Solution" (sort of a master project - the concept doesn't appear in VS6) which contains projects from different languages and links them together.
I believe that the compilation cascade issue is not in the new IDE, as the dependence analyzer is now all our own code (I think).
You can have CVF and Intel Visual Fortran on the same system, and they will each operate on their own. My own system has CVF/Visual Studio 6, Visual Studio.NET 2002 and 2003, with Intel Fortran and C++ integrated into the latter.
If you purchased Intel Fortran already, you get 12 months of support with free upgrades. That hasn't changed and I know of no plans to change it. After the year, you can renew for another year - the current price for that is $200. Intel uses the support subscription model which is different from the way CVF did things. Some customers will like this, some won't. Some didn't like the CVF way either. C'est la vie...
I expect the upgrade from CVF to Intel Visual Fortran to be the same $200. Note that Intel Visual Fortran will include Array Visualizer, which was only in the CVF Pro edition. IMSL will be available as an extra cost option, but it will not be anywhere near as cheap as it was with CVF. Visual Numerics has changed their pricing structure and we have to accomodate.
Support is handled differently, and better in many ways. Instead of an e-mail address, there's a web site (https://premier.intel.com/) where you enter your support request and can attach files, all in a secure environment. What's nice about this is that you can track the status of all your support requests, and get updated files all from within your web browser. The support team (of which I'm now a member) is very good and dedicated. You won't be always dealing with me directly, but I'll be there making sure you get the best possible support.
I think that's enough for tonight!
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Thanks for your answer, which is very reassuring.
Now that Intel will be providing its own dependency checker, which you suggest does not have the problems of the previous MS version, could Intel also provide an option to disable dependency checking when rebuilding from the IDE? There are so many situations when the programmer's judgement about the propagation of changes which would require complementary compilation of other modules is superior to any automatic procedure, and avoiding unnecessary work would save SO MUCH TIME. A simple option switch for dependency checking would be a MAJOR improvement.
Thanks for your answer, which is very reassuring.
Now that Intel will be providing its own dependency checker, which you suggest does not have the problems of the previous MS version, could Intel also provide an option to disable dependency checking when rebuilding from the IDE? There are so many situations when the programmer's judgement about the propagation of changes which would require complementary compilation of other modules is superior to any automatic procedure, and avoiding unnecessary work would save SO MUCH TIME. A simple option switch for dependency checking would be a MAJOR improvement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spoke with the IDE team leader this afternoon and she tells me that there is now way to bypass the dependency checker. I looked and indeed there is. One of the menu options for the project/solution is now "Link", which simply links what's there without recompiling anything. She also confirmed my statement that the dependency checker was all our own now and did not have the "if three things changed rebuild everything" problem that plagues some CVF users.
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's excellent, Steve. I'll try the new IVF as soon as it's released.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are referring to Intel Visual Fortran (aka 8.0), scheduled for release late this year. It's not a "patch".
However, I would expect 7.1 to be ok in this regard. If it isn't, please report it to Intel Premier Support.
Steve
However, I would expect 7.1 to be ok in this regard. If it isn't, please report it to Intel Premier Support.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have two CVF 6.6 licenses, Pro and Standard. I purchased two copies of IF 7 in March through the recent discounted upgrade offer. I'm not using IF 7 yet, but I made the purchase to secure my rights to a free upgrade to IVF.
Intel originally didn't know if it was going to offer Pro and Standard versions of IVF, but this update now says that it intends to do so. Will there be a mechanism to distribute IVF Pro to people who upgraded to IF 7 from CVF Pro and IVF Standard to those who upgraded to IF 7 from CVS Standard? I've asked this question before, but it was too soon to get an answer.
And by the way, has Intel heard anything from Norman Lawrence about whether he intends to update his Compaq Visual Fortran book for IVF, or is that even necessary? Won't the changes in the default calling standard change his examples?
Mike
Intel originally didn't know if it was going to offer Pro and Standard versions of IVF, but this update now says that it intends to do so. Will there be a mechanism to distribute IVF Pro to people who upgraded to IF 7 from CVF Pro and IVF Standard to those who upgraded to IF 7 from CVS Standard? I've asked this question before, but it was too soon to get an answer.
And by the way, has Intel heard anything from Norman Lawrence about whether he intends to update his Compaq Visual Fortran book for IVF, or is that even necessary? Won't the changes in the default calling standard change his examples?
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The current plans are for there to be an upgrade price for current CVF Pro users to get IMSL, which is all that Intel Visual Fortran Pro will add over the Standard edition. That price has not yet been set, but it will be substantial, given Visual Numerics' pricing to us, but you won't be able to do better elsewhere if you want IMSL 5.
We haven't heard from Norman Lawrence regarding plans for an updated book.
Steve
We haven't heard from Norman Lawrence regarding plans for an updated book.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Any chance that the "old" (CVF6.6) version of IMSL will work with the new IVF Standard edition? CMXL?
Greg
Any chance that the "old" (CVF6.6) version of IMSL will work with the new IVF Standard edition? CMXL?
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm pretty sure it won't link, as it makes calls to the CVF run-time libraries. You could probably fudge something by building a DLL that exported the routines you needed, though.
Steve
Steve
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