Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ptp-dev] Re: HPC Toolkit 
On May 5, 2005, at 10:44 AM, Rob Fowler wrote:


There are two main things we should do:

First, the HPCToolkit workflow should get integrated with
those parts of PTP for building and running apps.


Do you have any plans to visit LANL?  It would be nice
if someone could sit down with us and walk us through
the steps.  Brian Foote (Photran team) is visiting the
first week of June to talk about Fortran refactoring.
I also want to talk about using external tools for Fortran
parsing then too.  Are you interested in attending?

If not, perhaps Greg (or I) could visit Rice in June.


--  In the build phases, code should be compiled "-On -g"
to ensure that it's optimized at the right level and that
debugging symbols are generated.  The tools should check this,
encourage it, etc.


We build the eclipse tool chain so we can put in whatever
options are needed (including bloop).


--  If HPCToolkit is going to be used with an app, a rule
for running bloop (pronounced "bee loop") should be added
to the final linking for each load module each time it's rebuilt.


-- An interface is needed for running the toolchain.  Once set up,
     this stuff should be an easy, automated option each time the
     application is run.


We will be providing a parallel launch facility so whatever is needed
should be built into it.



-- We need configuration tools.  "hpcquick" is a Perl script that
   runs part of the tool chain and that generates a script that will
   re-run its actions, and  a default hpcview configuration file (an
   XML document) that can be edited later.   Hand editing of XML
   from scratch is painful, so we do a lot of cut-and-paste.  A GUI
   configuration tool is something that's been in a low-priority bin
   in our to-do list.


I assume this is outside of Eclipse.  But if configure/build of external
tools is outside of Eclipse, then a problem for us is knowing where
everything is.
Second, hpcviewer is a stand-alone Java program that uses the Swing toolkit. Running it from Eclipse makes sense, but we need also 
to have a version that runs on your laptop under any operating
system.

One concern with all of this is that we think it'll continue to
be necessary to continue to have stand-alone versions of
everything.


Hopefully eclipse stuff can be a thin wrapper that calls (or uses)
stand-alone versions.

Cheers,
Craig

Back to the top