- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
i'm working on a hugh Fortan project which is build through several Makefiels, so the regular approach of the static analysis will not work for me. Also I'm working on a Linux maschine, thats why the VS-solution will not work as well.
So I tried to use the specfile-approach, but inspxe-inject doesn't work. The spec-file is created but the content is empty
the command:
inspxe-inject -save-spec spec1.spec -- make
creates a soec file, that looks like:
# DO NOT EDIT THIS FILE!!!
# Source Checker Build Specification Format, version 1.0.0
Then I tried to use a simple example to check, if it is a problem of the code or of inspxe-inject.
program summation
implicit none
integer :: val1, val2
val1 = 1
val2 = 2
print*, "the result is: ", (val1+val2)
end
with the Makefile:
FC = ifort
#FCFLAGS = -openmp -shared-intel -shared-libgcc
all: main
main: main.f90
$(FC) $(FCFLAGS) main.f90 -o main
EXECUTABLES = main
clean::
rm -f main
does anyone has an idea what i did wrong? - what else can I try to do?
Thank you,
Kai
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Peter Wang (Intel) wrote:Hi Peter, thanks for your reply! Yes, for this example you're right. but this way, how i mentioned before, will not work for the real project I'm working on. because I can't change the build process of that program.Actually you don't need to use these internal command lines, use:
ifort -diag-enable sv3 main.f90
"r000sc" sub-directory will be generated in current directory, use:
inspxe-cl -report problems -r r000sc, or use inspxe-gui to open result.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Kai wrote:Assume that you will build many modules in a real project. If it is the case, you might do sveral times of SSA - module based, and open results for modules respectively.Quote:
Peter Wang (Intel) wrote:Actually you don't need to use these internal command lines, use:
ifort -diag-enable sv3 main.f90
"r000sc" sub-directory will be generated in current directory, use:
inspxe-cl -report problems -r r000sc, or use inspxe-gui to open result.Hi Peter,
thanks for your reply!
Yes, for this example you're right. but this way, how i mentioned before, will not work for the real project I'm working on. because I can't change the build process of that program.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![](/skins/images/D3C0B914909A6564BBB97F4AD1ED1973/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page