<br><div class="gmail_quote">On Mon, Nov 2, 2009 at 2:30 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><br></div>
Unfortunately it looks like -Tf implies -fixed too so it does not<br>
work with free-format sources unless -free is also added. We cannot<br>
add -free automatically because some sources might be fixed. The<br>
solution ties into another item on my todo-list: we need a source<br>
file property to mark every source as fixed or free format. It can<br>
default based on file extension. The property would be used both<br>
for adding "-fixed"/"-free" flags and to aid the dependency scanner<br>
in identifying comments.<br>
<br>
Summary: until the above is done we cannot add -Tf upstream :(<br><font color="#888888">
<br>
-Brad<br>
</font></blockquote></div><br>Thanks for looking into a more comprehensive correction. I consider this issue to be a failure of the Intel compiler. At least their Windows version allows you to specify additional extensions to treat as Fortran sources -- but no such luck under Linux. In addition to the -free/-fixed option based on file extenion, ifort also assumes preprocessed or not based on file extension. (.f vs .F). Yuck.<br>
<br>-kt<br><br>