Community
Participate
Working Groups
XLF toolchain is currently named "XLF Fortran on MacOS X" e.g. in org.eclipse.photran.managedbuilder.xlf.ui/plugin.properties three instances of Mac-specific names. I don't think anything is specific to Mac. ToolName.linker.macosx.xlf.fortran = MacOS X IBM XLF Fortran Linker # Build Model Names TargetName.xlf.fortran.macosx.exe=Executable (XLF Fortran on MacOS X) TargetName.xlf.fortran.macosx.so=Shared Library (XLF Fortran on MacOS X) TargetName.xlf.fortran.macosx.lib=Static Library (XLF Fortran on MacOS X) or is it? also # XLF tool names ToolName.compiler.xlf.fortran = IBM XLF Fortran Compiler ToolName.linker.xlf.fortran = IBM XLF Fortran Linker ToolName.linker.macosx.xlf.fortran = MacOS X IBM XLF Fortran Linker
Thanks, Beth. Two things... 1. While I'm at it, the correct name is "IBM XL Fortran", not "XLF Fortran", right? 2. Do you want these changes in 7.0.5 or just for Juno?
1. I think so, yes, "IBM XLF Fortran" 2. I don't have a strong preference, but first guess: I'd say just Juno. Since it's just a name change, let's leave it the same in 7.0/Indigo branch.
Correction: IBM XL Fortran as you said the first time.
I am hijacking this bug to cover some of the other changes we discussed as well. :-) In addition to the name change, * "-qsuffix=f=f90" should be removed from the default compiler options * the compiler and linker should be invoked via "xlf", not "xlf95"
I committed the following changes to HEAD: 1. All names are changed to "IBM XL Fortran" rather than "XLF Fortran", "XLF", etc. 2. There were two definitions of linker tools in plugin.xml, the first of which didn't appear to be used anywhere, so I removed it. 3. The command "xlf" is used to invoke the compiler and linker rather than "xlf95" 4. I removed the Shared Library options from the linker -- notably "-Wl,-dylib" which, AFAIK, is Mac OS X-specific (and only useful for building shared libraries, not executables) 5. I removed the Source options for the compiler tool. In particular, I removed the option that was setting "-qsuffix=f=f95" Note to self: There are several strings in plugin.properties that aren't used anywhere. Things I didn't change yet that are suspicious: 1. <tool natureFilter="cnature" -- shouldn't this reference the Fortran nature instead? 2. We need to seriously test the linker options. I wonder if they're all valid or not. I suspect that they were copied from the GNU toolchain and never tested. Supposedly, xlf will just pass them on to GNU ld, which actually does the linking, but it would be good to verify that they're all correct. 3. See Bug 346522 -- I bet it holds for the XLF toolchain
The "cnature" filter is correct. I fixed the XLF toolchain w.r.t. Bug 346522. Beth, when you get time, please try the tests with the new changes in HEAD and let me know if everything is OK. If so, I'll close this bug. Thanks.
For consistency, I am renaming the org.eclipse.photran.errorparsers.xlf plug-in to org.eclipse.photran.core.xlf (similar to org.eclipse.photran.core.intel for their error parser). I'm keeping the qualified error parser ID the same so as not to break backward compatibility.
Marking this closed/fixed for 8.0. Beth, please reopen or let me know if you need anything else from me on the XLF toolchain.
