<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Here is the LaTeX from the OMPD spec:<br>
<blockquote><tt>\section{OpenMP Runtime Interface}</tt><br>
<tt>\label{runtime-interface:sec}</tt><br>
<br>
<tt>As part of the OpenMP interface, OMPD requires that the OpenMP</tt><br>
<tt>runtime system provides a public variable
\verb|ompd_dll_locations|,</tt><br>
<tt>which is an \texttt{argv}-style vector of filename string
pointers that</tt><br>
<tt>provides the pathnames(s) of any compatible OMPD plugin</tt><br>
<tt>implementations (if any).</tt><br>
<tt>\texttt{ompd\_dll\_locations} must have \texttt{C} linkage.</tt><br>
<tt>The debugger uses the name verbatim, and in particular, will</tt><br>
<tt>not apply any name mangling befor performing the look up.</tt><br>
<tt>The pathnames may be relative or absolute.</tt><br>
<br>
<tt>\begin{quote}</tt><br>
<tt>\begin{lstlisting}</tt><br>
<tt>const char **ompd_dll_locations;</tt><br>
<tt>\end{lstlisting}</tt><br>
<tt>\end{quote}</tt><br>
<tt>\labeldef{dll-locations:def}</tt><br>
<br>
<tt>\noindent</tt><br>
<tt>%%%% The value of \verb|ompd_dll_locations| may be NULL initially,</tt><br>
<tt>%%%% but must be filled in before \verb|ompd_initialize| is
called.</tt><br>
<tt>%%%% After that,</tt><br>
<tt>\verb|ompd_dll_locations| shall point to a NULL-terminated</tt><br>
<tt>vector of zero or more NULL-terminated pathname strings.</tt><br>
<tt>There are no filename conventions for pathname strings.</tt><br>
<tt>The last entry in the vector shall be NULL. </tt><br>
<tt>The vector of string pointers must be fully initialized
\emph{before}</tt><br>
<tt>\texttt{ompd\_dll\_locations} is set to a non-NULL value,</tt><br>
<tt>such that if the debugger stops execution at any point</tt><br>
<tt>where \texttt{ompd\_dll\_locations} is non-NULL, then the vector</tt><br>
<tt>of strings it points to is valid and complete.</tt><br>
<br>
<tt>The programming model or architecture of the debugger (and hence</tt><br>
<tt>that of the required OMPD) might not match that of the target</tt><br>
<tt>OpenMP program.</tt><br>
<tt>It is the responsibility of the debugger to interpret the contents</tt><br>
<tt>of \texttt{ompd\_dll\_locations} to find a suitable OMPD that
matches</tt><br>
<tt>its own architectural characteristics.</tt><br>
<tt>On platforms that support different programming models</tt><br>
<tt>(\textit{e.g.}, 32 v. 64-bit), OpenMP implementers are encouraged</tt><br>
<tt>to provide OMPD implementations for all models, and which can
handle</tt><br>
<tt>targets of any model.</tt><br>
<tt>Thus, for example, a 32-bit debugger should be able to debug a
64-bit target</tt><br>
<tt>by loading a 32-bit OMPD that can manage a 64-bit OpenMP runtime.</tt><br>
<br>
<tt>The OpenMP runtime shall notify the debugger that</tt><br>
<tt>\texttt{ompd\_dll\_locations} is valid by calling:</tt><br>
<tt>\begin{quote}</tt><br>
<tt>\begin{lstlisting}</tt><br>
<tt>void ompd_dll_locations_valid ( void );</tt><br>
<tt>\end{lstlisting}</tt><br>
<tt>\end{quote}</tt><br>
<tt>\labeldef{dll-locations-valid:def}</tt><br>
<br>
<br>
<tt>\noindent</tt><br>
<tt>The debugger can receive notification of this event by planting</tt><br>
<tt>a breakpoint in this routine.</tt><br>
<tt>\texttt{ompd\_dll\_locations\_valid ()} has \texttt{C} linkage,</tt><br>
<tt>and the debugger will not apply name mangling before searching</tt><br>
<tt>for this routine.</tt><br>
</blockquote>
Cheers, John D.<br>
<br>
Kathryn Mohror wrote:
<blockquote cite="mid:000701d0d50f$d0718270$71548750$@llnl.gov"
type="cite">
<pre wrap="">Hi Jeff,
Yes, that is a good idea. I am not sure when I will get around to actually
moving all the content, so in the short term, I should at least put a
pointer to the new page on the old one...
Thanks!
Kathryn
_________________________________________________________________
Kathryn Mohror, <a class="moz-txt-link-abbreviated" href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a class="moz-txt-link-freetext" href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a>
Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA,
USA
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: Jeff Squyres (jsquyres) [<a class="moz-txt-link-freetext" href="mailto:jsquyres@cisco.com">mailto:jsquyres@cisco.com</a>]
Sent: Wednesday, August 12, 2015 7:56 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>; MPI Tool WG
Subject: Re: [mpiwg-tools] Meeting reminder: Thursday, 8/13
Kathryn --
If you didn't do so already, might I suggest that you remove the contents
</pre>
</blockquote>
<pre wrap=""><!---->of
</pre>
<blockquote type="cite">
<pre wrap="">the old wiki page and simply leave a pointer to the new one?
</pre>
<blockquote type="cite">
<pre wrap="">On Aug 12, 2015, at 10:44 AM, Kathryn Mohror <a class="moz-txt-link-rfc2396E" href="mailto:kathryn@llnl.gov"><kathryn@llnl.gov></a> wrote:
Hi everyone,
This is a reminder of our regular tools WG telecon this Thursday at
8:00 AM PDT, 11:00 EDT. You can access the webex information from the
</pre>
</blockquote>
<pre wrap="">wiki:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="https://bitbucket.org/mpiforum/toolswg/wiki/Meetings">https://bitbucket.org/mpiforum/toolswg/wiki/Meetings</a>
Note that the wiki page has moved! The old content remains on the
older wiki, but we are moving to a bitbucket. I am slowly
transitioning content over, and plan to put new content only on the
new wiki. Please let me know if you have any trouble accessing the new
</pre>
</blockquote>
<pre wrap="">wiki site:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="https://bitbucket.org/mpiforum/toolswg/wiki/Home">https://bitbucket.org/mpiforum/toolswg/wiki/Home</a>
Agenda:
QMPI - ~1st half hour
Debugger topics - ~2nd half hour
Talk to you soon!
Kathryn
</pre>
</blockquote>
<pre wrap="">__________________________________________________________
_______
</pre>
<blockquote type="cite">
<pre wrap="">Kathryn Mohror, <a class="moz-txt-link-abbreviated" href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a class="moz-txt-link-freetext" href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a>
Scalability Team @ Lawrence Livermore National Laboratory, Livermore,
CA, USA
_______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools</a>
</pre>
</blockquote>
<pre wrap="">
--
Jeff Squyres
<a class="moz-txt-link-abbreviated" href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>
For corporate legal information go to:
<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/">http://www.cisco.com/web/about/doing_business/legal/cri/</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
mpiwg-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools</a>
</pre>
</blockquote>
</body>
</html>