Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

VS 2010 bug(?)

WSinc
New Contributor I
‎04-16-2014 10:56 AM
380 Views
I had the main program called source01.f90, and extracted a routine with the intention of calling it something else. It called the extracted code source01.f90 ALSO - This is just an annoyance, but if someone isn't alert, it can lead to lost source code. For example if you tried to save BOTH of them it would lead to something getting clobbered. I was wondering if the problem was addressed and corrected later. My understanding is that I can't use the Fortran compiler with later versions of VS. Has that been addressed?
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎04-16-2014 11:34 AM
380 Views

How exactly did you "extract" it so that a source file name was generated? I can't get it to reuse a file name when it generates one, and if I try to save over an existing name deliberately, it warns me.

Each version of Visual Fortran supports some set of VS releases. Composer XE 2013 SP1 (compiler 14) supports VS2008, VS2010, VS2012 and VS2013. Our next major release will drop VS2008 support.

When you have installed a version, the integration will let you select up to two versions back. For more information, see:

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.