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

ifort message 10147

cecio
Novice
‎06-29-2009 06:08 AM
601 Views
Hi, what is:

ifort: warning: #10147 no action performed for specified file(s) ???

Where i can read about error and warning messages?

Thanks
0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎06-29-2009 06:32 AM
601 Views
Quoting - cecio

ifort: warning: #10147 no action performed for specified file(s) ???

Where i can read about error and warning messages?

I notice by Googling that this was answered as documentation pending, since last fall. If you're not getting this the usual ways, you should at least tell how you got the message. For example, ifort -c *.o (nothing to be done, as -c asks for .o files to be made), or ifort -S *.s
0 Kudos
Copy link
Ron_Green
Moderator
‎06-29-2009 07:45 AM
601 Views
Quoting - tim18
I notice by Googling that this was answered as documentation pending, since last fall. If you're not getting this the usual ways, you should at least tell how you got the message. For example, ifort -c *.o (nothing to be done, as -c asks for .o files to be made), or ifort -S *.s

In our database I see just a few instances of this warning. In one case, a user took a makefile designed for the PathScale compiler and simply changed the name of the compiler, leaving all the PathScale options. It's unknown which option(s) were in the original Makefile.

In the second case, a user had illegal names for the source files, .f95 and .F95 for example. Make sure your filenames have allowed extensions .f .F .f90, .F90.

ron
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.