Update web pages to include style sheets and referenced documents missed before.

llvm-svn: 191888
This commit is contained in:
Jim Cownie 2013-10-03 11:55:28 +00:00
parent 52cfb6a99a
commit 885d7fa8a4
5 changed files with 10613 additions and 13 deletions

104
openmp/www/README.txt Normal file
View File

@ -0,0 +1,104 @@
README for Intel(R) OpenMP* Runtime Library
===========================================
How to Build Documentation
==========================
The main documentation is in Doxygen* format, and this distribution
should come with pre-built PDF documentation in doc/Reference.pdf.
However, an HTML version can be built by executing:
% doxygen doc/doxygen/config
in this directory.
That will produce HTML documentation in the doc/doxygen/generated
directory, which can be accessed by pointing a web browser at the
index.html file there.
If you don't have Doxygen installed, you can download it from
www.doxygen.org.
How to Build the Intel(R) OpenMP* Runtime Library
=================================================
The Makefile at the top-level will attempt to detect what it needs to
build the Intel(R) OpenMP* Runtime Library. To see the default settings,
type:
make info
You can change the Makefile's behavior with the following options:
omp_root: The path to the top-level directory containing the top-level
Makefile. By default, this will take on the value of the
current working directory.
omp_os: Operating system. By default, the build will attempt to
detect this. Currently supports "linux", "macos", and
"windows".
arch: Architecture. By default, the build will attempt to
detect this if not specified by the user. Currently
supported values are
"32" for IA-32 architecture
"32e" for Intel(R) 64 architecture
"mic" for Intel(R) Many Integrated Core Architecture
If "mic" is specified then "icc" will be used as the
compiler, and appropriate k1om binutils will be used. The
necessary packages must be installed on the build machine
for this to be possible (but an Intel(R) Xeon Phi(TM)
coprocessor card is not required to build the library).
compiler: Which compiler to use for the build. Defaults to "icc"
or "icl" depending on the value of omp_os. Also supports
some versions of "gcc"* when omp_os is "linux". The selected
compiler should be installed and in the user's path. The
corresponding Fortran compiler should also be in the path.
See "Supported RTL Build Configurations" below for more
information on compiler versions.
mode: Library mode: default is "release". Also supports "debug".
To use any of the options above, simple add <option_name>=<value>. For
example, if you want to build with gcc instead of icc, type:
make compiler=gcc
Supported RTL Build Configurations
==================================
Supported Architectures: IA-32 architecture, Intel(R) 64, and
Intel(R) Many Integrated Core Architecture
-----------------------------------------------------------
| icc/icl | gcc |
--------------|------------------------------|--------------------------|
| Linux* OS | Yes(1,5) | Yes(2,4) |
| OS X* | Yes(1,3,4) | No |
| Windows* OS | Yes(1,4) | No |
-------------------------------------------------------------------------
(1) On IA-32 architecture and Intel(R) 64, icc/icl versions 12.x are
supported (12.1 is recommended).
(2) gcc version 4.6.2 is supported.
(3) For icc on OS X*, OS X* version 10.5.8 is supported.
(4) Intel(R) Many Integrated Core Architecture not supported.
(5) On Intel(R) Many Integrated Core Architecture, icc/icl versions 13.0
or later are required.
Front-end Compilers that work with this RTL
===========================================
The following compilers are known to do compatible code generation for
this RTL: icc/icl, gcc. See the documentation for more detail.
-----------------------------------------------------------------------
Notices
=======
*Other names and brands may be claimed as the property of others.

10413
openmp/www/Reference.pdf Normal file

File diff suppressed because it is too large Load Diff

27
openmp/www/content.css Normal file
View File

@ -0,0 +1,27 @@
html { margin: 0px; } body { margin: 8px; }
html, body {
padding:0px;
font-size:small; font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Verdana, Helvetica, sans-serif; background-color: #fff; color: #222;
line-height:1.5;
}
h1, h2, h3, tt { color: #000 }
h1 { padding-top:0px; margin-top:0px;}
h2 { color:#333333; padding-top:0.5em; }
h3 { padding-top: 0.5em; margin-bottom: -0.25em; color:#2d58b7}
li { padding-bottom: 0.5em; }
ul { padding-left:1.5em; }
/* Slides */
IMG.img_slide {
display: block;
margin-left: auto;
margin-right: auto
}
.itemTitle { color:#2d58b7 }
/* Tables */
tr { vertical-align:top }

View File

@ -32,19 +32,21 @@
<div id="content">
<!--*********************************************************************-->
<h1>"OpenMP*" Support for the OpenMP language</h1>
<h1>"OpenMP&reg;" Support for the OpenMP language</h1>
<!--*********************************************************************-->
<p>The OpenMP subproject of LLVM is intended to contain all of the
components required to build an executing OpenMP program that are
outside the compiler itself. Support for OpenMP 3.1 in Clang is in the
process of being promoted into the Clang mainline, and can be
found at <a href="http://clang-omp.github.io/">OpenMP/Clang</a>.
found at <a href="http://clang-omp.github.io/">OpenMP/Clang</a>.
</p>
<p>Here you can find the code for the runtime library against which
code compiled by the OpenMP/Clang compiler must be linked before it
can run.
can run. This code is also available
at <a href="http://openmprtl.org/">openmprtl.org</a>; we intend to
keep the different sites in sync.
</p>
<p>We are, however, still missing test code. Any contributions in
@ -65,9 +67,13 @@
<ul>
<li>Correctness as defined by the
<a href="http://www.openmp.org/mp-documents/OpenMP3.1.pdf">OpenMP
3.1 standard (PDF)</a> </li>
3.1 standard (PDF)</a> now, and <a href="http://www.openmp.org/mp-documents/OpenMP4.0.0.pdf">OpenMP
4.0 standard (PDF)</a> in the future.</li>
<li>High performance.</li>
<li>ABI compatibility Intel's existing OpenMP compiler.</li>
<li>ABI compatibility with <a href="http://gcc.gnu.org">Gcc</a> and
<a href="http://software.intel.com/en-us/intel-compilers">Intel's
existing OpenMP compilers.</a>
</li>
</ul>
<!--=====================================================================-->
@ -87,19 +93,17 @@
the Intel compiler.
</p>
<p>A full OS compatibility matrix is in a
<a href="runtime/README.txt">runtime/README.txt</a>
<p>A full OS compatibility matrix is in
<a href="README.txt">README.txt</a>
</p>
<!--=====================================================================-->
<h2 id="dir-structure">Current Status</h2>
<h2 id="dir-structure">Status</h2>
<!--=====================================================================-->
<p>Currently the runtime is built with either gcc or icc. Obviously
it would be good also to build with Clang. If anyone wants to
submit patches to do that (or replace the complicated historical
build system with CMake) that'd be great!
it would also be good to build with Clang.
</p>
@ -126,7 +130,7 @@
</ul>
<p>Full details of how to build are in the
<a href="runtime/README.txt">runtime/README.txt</a>
<a href="README.txt">README.txt</a>
</p>
<!--=====================================================================-->
@ -146,9 +150,22 @@
<!--=====================================================================-->
<ul>
<li><a href="runtime/doc/Reference.pdf">Runtime design (PDF)</a></li>
<li><a href="Reference.pdf">Runtime design (PDF)</a></li>
</ul>
<!--=====================================================================-->
<h2>Copyright notices</h2>
<!--=====================================================================-->
<ul>
<li>
The OpenMP name and the OpenMP logo are registered trademarks of the
OpenMP Architecture Review Board.
</li>
<li>
Intel is a trademark of Intel Corporation in the U.S. and/or other
countries.
</li>
</ul>
</div>
</body>
</html>

39
openmp/www/menu.css Normal file
View File

@ -0,0 +1,39 @@
/***************/
/* page layout */
/***************/
[id=menu] {
position:fixed;
width:25ex;
}
[id=content] {
/* ***** EDIT THIS VALUE IF CONTENT OVERLAPS MENU ***** */
position:absolute;
left:29ex;
padding-right:4ex;
}
/**************/
/* menu style */
/**************/
#menu .submenu {
padding-top:1em;
display:block;
}
#menu label {
display:block;
font-weight: bold;
text-align: center;
background-color: rgb(192,192,192);
}
#menu a {
padding:0 .2em;
display:block;
text-align: center;
background-color: rgb(235,235,235);
}
#menu a:visited {
color:rgb(100,50,100);
}