# [haiku-commits] buildtools: btrev43052 - ppl/doc cloog/test ppl cloog/isl ppl/src

• From: korli@xxxxxxxxxxxxxxxx
• To: haiku-commits@xxxxxxxxxxxxx
• Date: Sat, 6 Apr 2013 15:13:09 +0200 (CEST)

btrev43052 adds 2 changesets to branch 'master'
overview: http://cgit.haiku-os.org/buildtools/log/?qt=range&q=5873a06+%5Ef31d42d

----------------------------------------------------------------------------

df9ffb3: gcc: cherry picked patch for support of current CLooG

* cloog now uses CLOOG_LANGUAGE_C instead of LANGUAGE_C.
* graphite-clast-to-gimple.c (CLOOG_LANGUAGE_C): Provide if missing.
(set_cloog_options): Use it.

5873a06: imported PPL 0.11.1 and CLooG 0.18.0.

* these are dependencies for gcc 4 Graphite engine build.
* CLooG 0.18.0 includes ISL 0.11.1 which is the backend that the build script
enables.
* PPL is needed by GCC build even if it isn't the chosen backend.

[ Jerome Duval <jerome.duval@xxxxxxxxx> ]

----------------------------------------------------------------------------

3165 files changed, 1268447 insertions(+), 2 deletions(-)
cloog/.gitignore                                 |     44 +
cloog/.gitmodules                                |      6 +
cloog/ChangeLog                                  |     32 +
cloog/Makefile.am                                |    179 +
cloog/autoconf/Doxyfile.in                       |   1101 +
cloog/autoconf/c-ced.ssh                         |     81 +
cloog/autogen.sh                                 |      5 +
cloog/configure.ac                               |    263 +
cloog/doc/Makefile.am                            |      7 +
cloog/doc/SubmittingPatches                      |     41 +
cloog/doc/TODO                                   |     58 +
cloog/doc/cloog.texi                             |   2722 +
cloog/doc/images/basic.eps                       |    402 +
cloog/doc/images/basic.fig                       |    100 +
cloog/doc/images/basic.jpg                       |    Bin 0 -> 21180 bytes
cloog/doc/images/basic.pdf                       |    Bin 0 -> 40073 bytes
cloog/doc/images/basic.txt                       |     13 +
cloog/doc/images/tree.eps                        |    258 +
cloog/doc/images/tree.fig                        |     54 +
cloog/doc/images/tree.jpg                        |    Bin 0 -> 13713 bytes
cloog/doc/images/tree.pdf                        |    Bin 0 -> 4558 bytes
cloog/doc/images/tree.txt                        |     25 +
cloog/examples/example/example-isl.c             |     66 +
cloog/examples/example/example.c                 |     29 +
cloog/genversion.sh.in                           |     15 +
cloog/get_submodules.sh                          |      3 +
cloog/include/cloog/block.h                      |    117 +
cloog/include/cloog/clast.h                      |    176 +
cloog/include/cloog/cloog.h                      |     62 +
cloog/include/cloog/constraints.h                |    121 +
cloog/include/cloog/domain.h                     |    177 +
cloog/include/cloog/input.h                      |     27 +
cloog/include/cloog/int.h                        |    174 +
cloog/include/cloog/isl/backend.h                |     11 +
cloog/include/cloog/isl/cloog.h                  |     22 +
cloog/include/cloog/isl/constraintset.h          |     33 +
cloog/include/cloog/isl/domain.h                 |     36 +
cloog/include/cloog/loop.h                       |    120 +
cloog/include/cloog/matrix.h                     |     59 +
cloog/include/cloog/matrix/constraintset.h       |     28 +
cloog/include/cloog/names.h                      |    103 +
cloog/include/cloog/options.h                    |    169 +
cloog/include/cloog/pprint.h                     |     67 +
cloog/include/cloog/program.h                    |    116 +
cloog/include/cloog/state.h                      |     46 +
cloog/include/cloog/statement.h                  |     85 +
cloog/include/cloog/stride.h                     |     33 +
cloog/include/cloog/union_domain.h               |     52 +
cloog/include/cloog/version.h.in                 |     50 +
cloog/isl/.gitignore                             |     53 +
cloog/isl/.gitmodules                            |      3 +
cloog/isl/AUTHORS                                |     35 +
cloog/isl/ChangeLog                              |     98 +
cloog/isl/Makefile.am                            |    300 +
cloog/isl/autogen.sh                             |      2 +
cloog/isl/basis_reduction_tab.c                  |    243 +
cloog/isl/basis_reduction_templ.c                |    357 +
cloog/isl/bound.c                                |    278 +
cloog/isl/bound_test.sh.in                       |     35 +
cloog/isl/cat.c                                  |     58 +
cloog/isl/closure.c                              |     34 +
cloog/isl/codegen.c                              |    138 +
cloog/isl/codegen_test.sh.in                     |     15 +
cloog/isl/configure.ac                           |    220 +
cloog/isl/doc/Makefile.am                        |     17 +
cloog/isl/doc/SubmittingPatches                  |     41 +
cloog/isl/doc/chicago.bst                        |   1726 +
cloog/isl/doc/chicago.sty                        |    320 +
cloog/isl/doc/implementation.tex                 |   2036 +
cloog/isl/doc/isl.bib                            |    313 +
cloog/isl/doc/manual.tex                         |     75 +
cloog/isl/doc/mypod2latex                        |     14 +
cloog/isl/doc/user.pod                           |   6109 +
cloog/isl/include/isl/aff.h                      |    566 +
cloog/isl/include/isl/aff_type.h                 |     22 +
cloog/isl/include/isl/arg.h                      |    314 +
cloog/isl/include/isl/ast.h                      |    183 +
cloog/isl/include/isl/ast_build.h                |     90 +
cloog/isl/include/isl/band.h                     |     51 +
cloog/isl/include/isl/blk.h                      |     40 +
cloog/isl/include/isl/config.h.in                |      3 +
cloog/isl/include/isl/constraint.h               |    134 +
cloog/isl/include/isl/ctx.h                      |    243 +
cloog/isl/include/isl/dim.h                      |    122 +
cloog/isl/include/isl/flow.h                     |     75 +
cloog/isl/include/isl/hash.h                     |     79 +
cloog/isl/include/isl/id.h                       |     35 +
cloog/isl/include/isl/ilp.h                      |     34 +
cloog/isl/include/isl/int.h                      |    136 +
cloog/isl/include/isl/list.h                     |     67 +
cloog/isl/include/isl/local_space.h              |     78 +
cloog/isl/include/isl/lp.h                       |     50 +
cloog/isl/include/isl/map.h                      |    654 +
[ *** stats truncated: 3066 lines dropped *** ]

############################################################################

Commit:      df9ffb3a0f2d1a0a07f341c1598e677e1deffb12
URL:         http://cgit.haiku-os.org/buildtools/commit/?id=df9ffb3
Author:      Jerome Duval <jerome.duval@xxxxxxxxx>
Date:        Sat Apr  6 12:43:25 2013 UTC

gcc: cherry picked patch for support of current CLooG

* cloog now uses CLOOG_LANGUAGE_C instead of LANGUAGE_C.
* graphite-clast-to-gimple.c (CLOOG_LANGUAGE_C): Provide if missing.
(set_cloog_options): Use it.

----------------------------------------------------------------------------

diff --git a/gcc/gcc/graphite-clast-to-gimple.c
b/gcc/gcc/graphite-clast-to-gimple.c
index 41356dc..9010f09 100644
--- a/gcc/gcc/graphite-clast-to-gimple.c
+++ b/gcc/gcc/graphite-clast-to-gimple.c
@@ -1,5 +1,5 @@
/* Translation of CLAST (CLooG AST) to Gimple.
-   Copyright (C) 2009, 2010 Free Software Foundation, Inc.
+   Copyright (C) 2009, 2010, 2011 Free Software Foundation, Inc.
Contributed by Sebastian Pop <sebastian.pop@xxxxxxx>.

This file is part of GCC.
@@ -40,6 +40,10 @@ along with GCC; see the file COPYING3.  If not see
#include "graphite-dependences.h"
#include "graphite-cloog-compat.h"

+#ifndef CLOOG_LANGUAGE_C
+#define CLOOG_LANGUAGE_C LANGUAGE_C
+#endif
+
/* This flag is set when an error occurred during the translation of
CLAST to Gimple.  */
static bool gloog_error;
@@ -1367,7 +1371,7 @@ set_cloog_options (void)
/* Change cloog output language to C.  If we do use FORTRAN instead, cloog
will stop e.g. with "ERROR: unbounded loops not allowed in FORTRAN.", if
we pass an incomplete program to cloog.  */
-  options->language = LANGUAGE_C;
+  options->language = CLOOG_LANGUAGE_C;

/* Enable complex equality spreading: removes dummy statements
(assignments) in the generated code which repeats the

############################################################################

Revision:    btrev43052
Commit:      5873a060ca0b72b568f4a183d93604b2280503dc
URL:         http://cgit.haiku-os.org/buildtools/commit/?id=5873a06
Author:      Jerome Duval <jerome.duval@xxxxxxxxx>
Date:        Sat Apr  6 13:05:27 2013 UTC

imported PPL 0.11.1 and CLooG 0.18.0.

* these are dependencies for gcc 4 Graphite engine build.
* CLooG 0.18.0 includes ISL 0.11.1 which is the backend that the build script
enables.
* PPL is needed by GCC build even if it isn't the chosen backend.

----------------------------------------------------------------------------

diff --git a/cloog/.gitignore b/cloog/.gitignore
new file mode 100644
index 0000000..eb9839f
--- /dev/null
+++ b/cloog/.gitignore
@@ -0,0 +1,44 @@
+# Ignore objects and archives.
+*.[oa]
+# library description files
+*.lo
+*.la
+
+.deps/
+.libs/
+Makefile
+Makefile.in
+aclocal.m4
+autoconf/Doxyfile
+autoconf/config.guess
+autoconf/config.sub
+autoconf/depcomp
+autoconf/install-sh
+autoconf/ltmain.sh
+autoconf/missing
+autom4te.cache/
+./cloog
+cloog-isl-uninstalled.pc
+cloog-isl-uninstalled.sh
+cloog-isl.pc
+cloog-isl.pc.in
+config.log
+config.status
+configure
+doc/Makefile
+doc/Makefile.in
+doc/gitversion.texi
+genversion.sh
+libtool
+m4/libtool.m4
+m4/ltoptions.m4
+m4/ltsugar.m4
+m4/ltversion.m4
+m4/lt~obsolete.m4
+source/version.c
+test/.deps/
+test/Makefile
+test/Makefile.in
+test/generate_test
+version.h
+include/cloog/version.h
diff --git a/cloog/.gitmodules b/cloog/.gitmodules
new file mode 100644
index 0000000..4beaf01
--- /dev/null
+++ b/cloog/.gitmodules
@@ -0,0 +1,6 @@
+[submodule "isl"]
+       path = isl
+       url = git://repo.or.cz/isl.git
+[submodule "osl"]
+       path = osl
+       url = git://repo.or.cz/openscop.git
diff --git a/cloog/ChangeLog b/cloog/ChangeLog
new file mode 100644
index 0000000..8b65ff1
--- /dev/null
+++ b/cloog/ChangeLog
@@ -0,0 +1,32 @@
+version: 0.18.0
+date: Thu Dec 20 17:50:41 CET 2012
+changes:
+       - Update to isl 0.11.1
+       - clast annotations for openmp and vectorization
+       - statement-wise loop separation
+       - clast traversal and node filtering support
+       - Do not call some deprecated isl functions
+       - Support for OpenSCoP coordinates extension
+
+version: 0.17.0
+date: Mon Dec 12 00:51:44 CET 2011
+changes:
+       - Support openscop as input format
+       - update isl backend to changes in isl 0.08
+       - Add CLOOG_ prefix to LANGUAGE defines in public header files
+       - Replace cloog_union_domain_from_isl_union_set() with
+         cloog_union_domain_from_isl_set()
+       - Allow to build CLooG from gmp build directory
+       - Smaller improvements
+
+version: 0.16.3
+date: Wed Jul 13 18:18:19 CEST 2011
+changes:
+       - update isl backend to recent changes in isl
+       - add support for unrolling
+---
+version: 0.16.2
+date: Sun Mar 20 15:51:13 CET 2011
+changes:
+       - update isl backend to recent changes in isl
+       - improved output in case of stride detection
new file mode 100644
index 0000000..8f87b3a
--- /dev/null
@@ -0,0 +1,458 @@
+                 GNU LESSER GENERAL PUBLIC LICENSE
+                      Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+                           Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+free software--to make sure the software is free for all its users.
+
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+entire combination fits its criteria of freedom.  The Lesser General
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+are the reason we use the ordinary General Public License for many
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+                 GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+  6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    e) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+distribute the Library is void, and will automatically terminate your
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+  9. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+
+  11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded.  In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation.  If the Library does not specify a
+the Free Software Foundation.
+
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission.  For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this.  Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+                           NO WARRANTY
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+                    END OF TERMS AND CONDITIONS
diff --git a/cloog/Makefile.am b/cloog/Makefile.am
new file mode 100644
index 0000000..1749c95
--- /dev/null
+++ b/cloog/Makefile.am
@@ -0,0 +1,179 @@
+#
+#   /**-------------------------------------------------------------------**
+#    **                              CLooG                                **
+#    **-------------------------------------------------------------------**
+#    **                           makefile.in                             **
+#    **-------------------------------------------------------------------**
+#    **                   First version: october 25th 2001                **
+#    **-------------------------------------------------------------------**/
+#
+# makefile.in (or makefile if generated) of CLooG, the Chunky LOOp Generator.
+# makefile.in is not a makefile, you must run the 'configure' shellscript to
+# generate the makefile thanks to this file.
+
+#/*****************************************************************************
+# *               CLooG : the Chunky Loop Generator (experimental)            *
+# *****************************************************************************
+# *                                                                           *
+# * Copyright (C) 2001 Cedric Bastoul                                         *
+# *                                                                           *
+# * This library is free software; you can redistribute it and/or             *
+# * modify it under the terms of the GNU Lesser General Public                *
+# * version 2.1 of the License, or (at your option) any later version.        *
+# *                                                                           *
+# * This library is distributed in the hope that it will be useful,           *
+# * but WITHOUT ANY WARRANTY; without even the implied warranty of            *
+# * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU         *
+# * Lesser General Public License for more details.                           *
+# *                                                                           *
+# * You should have received a copy of the GNU Lesser General Public          *
+# * License along with this library; if not, write to the Free Software       *
+# * Foundation, Inc., 51 Franklin Street, Fifth Floor,                        *
+# * Boston, MA  02110-1301  USA                                               *
+# *                                                                           *
+# * CLooG, the Chunky Loop Generator                                          *
+# * Written by Cedric Bastoul, Cedric.Bastoul@xxxxxxxx                        *
+# *                                                                           *
+#
*****************************************************************************/
+if BUNDLED_ISL
+    MAYBE_ISL = isl
+    ISL_LA = $(top_builddir)/isl/libisl.la +endif + +if BUNDLED_OSL + MAYBE_OSL = osl + OSL_LA =$(top_builddir)/osl/libosl.la
+endif
+
+SUBDIRS = $(MAYBE_ISL)$(MAYBE_OSL) . doc test
+DIST_SUBDIRS = $(MAYBE_ISL)$(MAYBE_OSL) . doc test
+
+ACLOCAL_AMFLAGS = -I m4
+
+FORCE:
+isl/libisl.la: FORCE
+       cd isl; $(MAKE)$(AM_MAKEFLAGS) libisl.la
+
+if NO_ISL
+CLOOG =
+LIBCLOOG =
+else
+CLOOG = cloog
+LIBCLOOG = libcloog-isl.la
+endif
+bin_PROGRAMS = $(CLOOG) +lib_LTLIBRARIES =$(LIBCLOOG)
+
+if NEED_GET_MEMORY_FUNCTIONS
+GET_MEMORY_FUNCTIONS=source/mp_get_memory_functions.c
+endif
+
+SOURCES_CORE = \
+       $(GET_MEMORY_FUNCTIONS) \ + source/block.c \ + source/clast.c \ + source/matrix.c \ + source/state.c \ + source/input.c \ + source/int.c \ + source/loop.c \ + source/names.c \ + source/options.c \ + source/pprint.c \ + source/program.c \ + source/statement.c \ + source/stride.c \ + source/union_domain.c \ + source/version.c + +DEFAULT_INCLUDES = -I. +INCLUDES = -I$(top_builddir)/include -I$(top_srcdir)/include +AM_CFLAGS =$(CFLAGS_WARN)
+libcloog_isl_la_CPPFLAGS = @ISL_CPPFLAGS@ @OSL_CPPFLAGS@
+libcloog_isl_la_LDFLAGS = -version-info @versioninfo@ \
+       -rpath $(libdir) @ISL_LDFLAGS@ @OSL_LDFLAGS@ +libcloog_isl_la_LIBADD = @ISL_LIBS@ @OSL_LIBS@$(ISL_LA) $(OSL_LA) +libcloog_isl_la_SOURCES = \ +$(SOURCES_CORE) \
+       source/isl/domain.c \
+       source/isl/constraints.c \
+       source/isl/backend.c
+cloog_DEPENDENCIES = libcloog-isl.la
+cloog_SOURCES = source/cloog.c
+
+       include/cloog/block.h \
+       include/cloog/clast.h \
+       include/cloog/cloog.h \
+       include/cloog/input.h \
+       include/cloog/int.h \
+       include/cloog/matrix.h \
+       include/cloog/state.h \
+       include/cloog/domain.h \
+       include/cloog/loop.h \
+       include/cloog/constraints.h \
+       include/cloog/names.h \
+       include/cloog/options.h \
+       include/cloog/pprint.h \
+       include/cloog/program.h \
+       include/cloog/statement.h \
+       include/cloog/stride.h \
+       include/cloog/union_domain.h \
+       include/cloog/version.h
+
+pkgmatrixincludedir = $(pkgincludedir)/matrix +pkgmatrixinclude_HEADERS = \ + include/cloog/matrix/constraintset.h + +pkgislincludedir =$(pkgincludedir)/isl
+       include/cloog/isl/backend.h \
+       include/cloog/isl/cloog.h \
+       include/cloog/isl/domain.h \
+       include/cloog/isl/constraintset.h
+
+version.h: @GIT_INDEX@
+       echo '#define CLOOG_HEAD "'$(top_builddir)/genversion.sh'"' >$@
+
+EXTRA_DIST = \
+       autoconf/Doxyfile.in \
+       source/matrix/constraintset.c \
+       doc/cloog.texi \
+       doc/images \
+       examples
+
+install-data-local:
+       @test -z "$(pkgconfig_libdir)" ||$(mkdir_p)
"$(DESTDIR)$(pkgconfig_libdir)"
+       $(INSTALL_DATA)$(pkgconfig_libfile)
"$(DESTDIR)$(pkgconfig_libdir)/$(pkgconfig_libfile)" + +uninstall-local: + rm -f "$(DESTDIR)$(pkgconfig_libdir)/$(pkgconfig_libfile)"
+
+dist-hook:
+       rm -f $(distdir)/test/Makefile +$(top_builddir)/genversion.sh > $(distdir)/CLOOG_HEAD + (cd doc; make cloog.pdf) && cp doc/cloog.pdf$(distdir)/doc/
+
+#/*****************************************************************************
+# *                                   Rules                                   *
+#
*****************************************************************************/
+
+valcheck:
+       $(MAKE) valgrind -C test + +total: + @echo " /*-----------------------------------------------*" + @echo " * CLooG *" + @echo " *-----------------------------------------------*/" +$(MAKE) uninstall
+       $(MAKE) clean +$(MAKE)
+       $(MAKE) install + +doc: + @echo " /*-----------------------------------------------*" + @echo " * Generating CLooG's documentation *" + @echo " *-----------------------------------------------*/" + doxygen ./autoconf/Doxyfile diff --git a/cloog/README b/cloog/README new file mode 100644 index 0000000..7003a2b --- /dev/null +++ b/cloog/README @@ -0,0 +1,203 @@ +# +# /**-------------------------------------------------------------------** +# ** CLooG ** +# **-------------------------------------------------------------------** +# ** The Chunky Loop Generator ** +# **-------------------------------------------------------------------** +# ** First version of this file: january 22th 2002 ** +# **-------------------------------------------------------------------**/ +# + +For complete informations about this software, how to build and use it, +please see the postscript file in the ./doc subdirectory (a pdf version +is available in the web site). + +Overview : +I. Description +II. Building CLooG +III. Options +IV. Running CLooG +V. General Questions + +# **-------------------------------------------------------------------** +# ** I. Description ** +# **-------------------------------------------------------------------**/ + +CLooG is a software which generates loops for scanning Z-polyhedra. That is, +CLooG finds the code or pseudo-code where each integral point of one or more +parametrized polyhedron or parametrized polyhedra union is reached. CLooG is +designed to avoid control overhead and to produce a very efficient code. + +Its input is some data on the polyhedra to scan, basically the system of +affine inequalities that define them, and a context that defines some +properties known on the parameters if any. The output is the pseudo scanning +code. Many facilities are provided to generate a near-to-be-compileable code, +and every useful functions to generate the code may be called from the CLooG +library. + + INPUT | OUTPUT +(fortunately not exactly the input, | (the real one, with default options) + check test/readme.cloog for the | + real input for that problem !) | + | + j^ i>=2 | + | | j<=n+2-i | + | |\ | i<=n | + | | \ | | + m-+-****---+-j<=m | for (i=2;i<=n;i++) { + | ***** | | for (j=2;j<=min(m,-i+n+2);j++) { + | ****** | ==> S1 ; + | *******| | } + 2-+-********-j>=2 | } + | | |\ | + 0-+-+------+--->i | + | | | | + 0 2 n | + | + Context : n>=2 | + m>=2 | + System : 2<=i<=n | + 2<=j<=m | + j<=n+2-i | + +# **-------------------------------------------------------------------** +# ** II. Building CLooG ** +# **-------------------------------------------------------------------**/ + +If you obtained CLooG from the git repository, then you first +need to obtain the submodules and create a configure script. + + ./get_submodules.sh + ./autogen.sh + +The first step is only needed if you plan on using the isl backend. + +The configure shell script attempts to guess correct values for various +system-dependent variables used during compilation. It uses those values to +create a Makefile. The file configure.ac is used to create configure by a +program called autoconf. You only need configure.ac if you want to change +it or regenerate configure using a newer version of autoconf. + +The simplest way to compile this package is: +cd to the directory containing the package's source code and type + + ./configure + +to configure the package for your system (while running, configure prints +some messages telling which features it is checking for). To compile the +package, type + + make + + +to install the program and/or the library, type + + make install + +you can remove the program binaries and object files from the source code +directory by typing + + make clean + +To also remove the files that configure created (so you can compile the +package for a different kind of computer) type + + make distclean + +# **-------------------------------------------------------------------** +# ** III. Options ** +# **-------------------------------------------------------------------**/ + +By default, make will install the package's files in /usr/local/bin, +/usr/local/lib, etc. You can specify an installation prefix other than +/usr/local by giving onfigure the option --prefix=PATH. + +By default, configure will use the isl that comes bundled with CLooG. +Using the --with-isl option of configure the user can specify that "no" isl, +a previously installed ("system") isl or a "build" isl should be used. +In the latter case, the user should also specify the build location +using --with-isl-builddir=PATH. In case of an installed isl, +the installation location can be specified using the +--with-isl-prefix=PATH and --with-isl-exec-prefix=PATH options of configure. + +By default, configure will seek the PolyLib in standard locations. +If necessary, you can specify the PolyLib's path by giving configure the +option --with-polylib-prefix=PATH and/or --with-polylib-exec-prefix=PATH. + +By default, configure will seek the GMP library in standard locations. +If necessary, you can specify the GMP's path by giving configure the +option --with-gmp-prefix=PATH and/or --with-gmp-exec-prefix=PATH. + +By default, when using the PolyLib backend, +CLooG and its library are built using 64 bits integer +representation. You can choose to specify explicitly others integer +representations by using: +--with-bits=32 for 32 bits integers, +--with-bits=64 for 64 bits integers (default), +--with-bits=gmp for multiple precision integers. + +# **-------------------------------------------------------------------** +# ** IV. Running CLooG ** +# **-------------------------------------------------------------------**/ + +To run CLooG, simply type 'cloog', optionally followed by the name of an +input file. You can type 'cloog -h' or 'cloog --help' for some help. +For more informations, please check the ./doc subdirectory. + +# **-------------------------------------------------------------------** +# ** V. General Questions ** +# **-------------------------------------------------------------------**/ + +1. What does CLooG means ? + +CLooG is the Chunky LOOp Generator, Chunky is an automatic loop optimizer for +data locality. CLooG is a completely independent part of the Chunky project. +Pronounce 'CLooG' as 'klug', which means 'sly' in german :-). + +2. CLooG do not compile, what should I do ? + +CLooG should compile everywhere (assuming that PolyLib is still there), thus +there is a problem or the documentation is not clear, in both case it is +necessary to ask the author(s) ! + +3. I need a feature that CLooG do not implement, what should I do ? + +There are two ways. First, CLooG is a LGPL software and library. So you +are welcome to improve it yourself ;-) ! Many project have been successful, it +is -maybe- a sign that this is not too hard to put your hands inside the +source. Second, just ask the author(s) :-) ! Maybe a lot of people would be +interessed by such feature, maybe many people asked for it before, maybe it's +trivial to implement (and even)... Please just never hesitate to ask the +author(s) ! + +4. I implemented a cool feature, can I submit it ? + +Obviously you are welcome to send the author(s) any improvement. But obviously +we are quite careful with readability, correctness and stability, and the +author(s) will read, check and check again any contribution before including it. +Thus, it can take time... There are few basic rules to write contributions: +- (1) Do never change the indentation of any part of the code that is not yours. +- (2) Do never send codes that use more than 80 columns. +- (3) Do never send codes without a lot of comments in (bad or good) english. +- (4) Do never send codes with obscure and/or non-english variable names. +- (5) Use C89, just C, only C (note: "//" comments are not C89, + variable declaration elsewhere than at the beginning of a block, is not C89). +- (6) Read doc/SubmittingPatches +Please understand that in order to live for a long time, and to be used in many +projects the very first priority for CLooG is to be readable and documented. + +5. Is CLooG bug free ? + +No, who can ? ClooG is a complex program, and we do not pretend it to be bug +free. Nevertheless because it has been tested and tested, we are fairly sure +that CLooG results with default options have good chances to be satisfactory. +If you find a result that looks strange, inadequate or incorrect, please send: +- (1) The input file to the author(s). +- (2) The output. +- (3) The first line given by typing 'cloog -v'. +- (4) All your command line options to achieve the result. +We will try to explain the result or to fix the problem as soon as possible. + +6. How can I contact the author(s) ? + +Just send a mail to cloog-development@xxxxxxxxxxxxxxxx diff --git a/cloog/autoconf/Doxyfile.in b/cloog/autoconf/Doxyfile.in new file mode 100644 index 0000000..fa02ac7 --- /dev/null +++ b/cloog/autoconf/Doxyfile.in @@ -0,0 +1,1101 @@ +# Doxyfile 1.3.5 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = CLooG + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = @RELEASE@ + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = doc/source + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, +# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en +# (Japanese with English messages), Korean, Norwegian, Polish, Portuguese, +# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. + +OUTPUT_LANGUAGE = English + +# This tag can be used to specify the encoding used in the generated output. +# The encoding is not always determined by the language that is chosen, +# but also whether or not the output is meant for Windows or non-Windows users. +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES +# forces the Windows encoding (this is the default for the Windows binary), +# whereas setting the tag to NO uses a Unix-style encoding (the default for +# all platforms other than Windows). + +USE_WINDOWS_ENCODING = NO + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is used +# as the annotated text. Otherwise, the brief description is used as-is. If left +# blank, the following values are used ("$name" is automatically replaced with
the
+# name of the entity): "The $name class" "The$name widget" "The $name file" +# "is" "provides" "specifies" "contains" "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = YES + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited +# members of a class in the documentation of that class as if those members were +# ordinary class members. Constructors, destructors and assignment operators of +# the base classes will not be shown. + +INLINE_INHERITED_MEMB = YES + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = NO + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. It is allowed to use relative paths in the argument list. + +STRIP_FROM_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like the Qt-style comments (thus requiring an +# explicit @brief command for a brief description. + +JAVADOC_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the DETAILS_AT_TOP tag is set to YES then Doxygen +# will output the detailed description near the top, like JavaDoc. +# If set to NO, the detailed description appears after the member +# documentation. + +DETAILS_AT_TOP = NO + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 8 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources +# only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources +# only. Doxygen will then generate output that is more tailored for Java. +# For instance, namespaces will be presented as packages, qualified scopes +# will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +EXTRACT_ALL = YES + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = YES + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = YES + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = NO + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = YES + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = YES + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = YES + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the$file, $line, and$text
+# tags, which will be replaced by the file and line number from which the
+# warning originated and the warning text.
+
+WARN_FORMAT            = "$file:$line: text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = +#WARN_LOGFILE = doc/doxygen.log + + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = source \ + include/cloog + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp +# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc + +FILE_PATTERNS = + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = NO + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories +# that are symbolic links (a Unix filesystem feature) are excluded from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. + +EXCLUDE_PATTERNS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command <filter> <input-file>, where <filter> +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. + +INPUT_FILTER = + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +SOURCE_BROWSER = NO + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES (the default) +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = YES + +# If the REFERENCES_RELATION tag is set to YES (the default) +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = YES + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = YES + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +ALPHABETICAL_INDEX = NO + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be +# generated containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. + +GENERATE_TREEVIEW = NO + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +GENERATE_LATEX = YES + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = NO + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = NO + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = YES + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. This is useful +# if you want to understand what is going on. On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = YES + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_PREDEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. + +PREDEFINED = + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse the +# parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::addtions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or +# super classes. Setting the tag to NO turns the diagrams off. Note that this +# option is superseded by the HAVE_DOT option below. This is only a fallback. It is +# recommended to install and use dot, since it yields more powerful graphs. + +CLASS_DIAGRAMS = YES + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = YES + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = YES + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will +# generate a call dependency graph for every global function or class method. +# Note that enabling this option will significantly increase the time of a run. +# So in most cases it will be better to enable call graphs for selected +# functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found on the path. + +DOT_PATH = /usr/bin/ + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +# DOTFILE_DIRS = src + +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width +# (in pixels) of the graphs generated by dot. If a graph becomes larger than +# this value, doxygen will try to truncate the graph, so that it fits within +# the specified constraint. Beware that most browsers cannot cope with very +# large images. + +MAX_DOT_GRAPH_WIDTH = 1024 + +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height +# (in pixels) of the graphs generated by dot. If a graph becomes larger than +# this value, doxygen will try to truncate the graph, so that it fits within +# the specified constraint. Beware that most browsers cannot cope with very +# large images. + +MAX_DOT_GRAPH_HEIGHT = 1024 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes that +# lay further from the root node will be omitted. Note that setting this option to +# 1 or 2 may greatly reduce the computation time needed for large code bases. Also +# note that a graph may be further truncated if the graph's image dimensions are +# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). +# If 0 is used for the depth value (the default), the graph is not depth-constrained. + +MAX_DOT_GRAPH_DEPTH = 0 + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Configuration::addtions related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = NO diff --git a/cloog/autoconf/c-ced.ssh b/cloog/autoconf/c-ced.ssh new file mode 100644 index 0000000..cc38b70 --- /dev/null +++ b/cloog/autoconf/c-ced.ssh @@ -0,0 +1,81 @@ +# To print the code correctly : a2ps --pretty-print=c-ced.ssh + +# Style sheet for C +# Copyright (c) 1995-2000 Akim Demaille, Miguel Santana +# + +# +# This file is part of a2ps. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; see the file COPYING. If not, write to +# the Free Software Foundation, 59 Temple Place - Suite 330, +# Boston, MA 02111-1307, USA. +# + +style C is +requires a2ps 4.13 + +written by "Akim Demaille <akim@xxxxxxxxxxxxxxx>" +version is 1.6 +documentation is + "This style does not highlight the function definitions." + "Another style which highlights them, GNUish C, is provided (gnuc.ssh)." + "It works only if you respect some syntactic conventions." +end documentation + +alphabets are + "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_#%"
+
+case sensitive
+
+ancestors are
+  cpp
+end ancestors
+
+keywords in Keyword are
+   double, enum, void, int, long, FILE, struct, char, signed, float,
+   short, unsigned
+end keywords
+
+keywords in Keyword_strong are
+   auto, "case", const, continue, do, inline, extern, for, register,
+   return, switch, union, goto, typedef, sizeof, typeof, volatile, static,
+   NULL, default, break, if, while, else
+end keywords
+
+optional operators are
+  (/(case)([   ]+)(.+)([       ]*:)/
+   \1 Keyword_strong, \2 Plain, \3 Label, \4 Plain)
+end operators
+
+optional operators are
+   -> \rightarrow,
+   && \wedge,
+   || \vee,
+   != \neq,
+   == \equiv,
+   # We need to protect these, so that <= is not replaced in <<=
+   <<=,
+   >>=,
+   <= \leq,
+   >= \geq,
+   ! \not
+end operators
+
+sequences are
+    "/*" Comment "*/",
+    "//" Comment
+end sequences
+
+end style
diff --git a/cloog/autogen.sh b/cloog/autogen.sh
new file mode 100755
index 0000000..661ece1
--- /dev/null
+++ b/cloog/autogen.sh
@@ -0,0 +1,5 @@
+#!/bin/sh
+autoreconf -i
+if test -f isl/autogen.sh; then
+       (cd isl; ./autogen.sh)
+fi
diff --git a/cloog/configure.ac b/cloog/configure.ac
new file mode 100644
index 0000000..0b36302
--- /dev/null
+++ b/cloog/configure.ac
@@ -0,0 +1,263 @@
+
+dnl /**-------------------------------------------------------------------**
+dnl  **                              CLooG                                **
+dnl  **-------------------------------------------------------------------**
+dnl  **                           configure.ac                            **
+dnl  **-------------------------------------------------------------------**
+dnl  **                   First version: august 7th 2002                  **
+dnl  **-------------------------------------------------------------------**/
+dnl
+dnl Input file for autoconf to build a configuration shellscript.
+dnl To build the configure script from the CLooG's top-level directory, use
+dnl autoconf -l autoconf autoconf/configure.in > configure
+dnl if it doesn't work (invalid option -l) try -I instead
+dnl autoconf -I autoconf autoconf/configure.in > configure
+
+dnl /**************************************************************************
+dnl *               CLooG : the Chunky Loop Generator (experimental)          *
+dnl ***************************************************************************
+dnl *                                                                         *
+dnl * Copyright (C) 2001 Cedric Bastoul                                       *
+dnl *                                                                         *
+dnl * This library is free software; you can redistribute it and/or           *
+dnl * modify it under the terms of the GNU Lesser General Public              *
+dnl * version 2.1 of the License, or (at your option) any later version.      *
+dnl *                                                                         *
+dnl * This library is distributed in the hope that it will be useful,         *
+dnl * but WITHOUT ANY WARRANTY; without even the implied warranty of          *
+dnl * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU       *
+dnl * Lesser General Public License for more details.                         *
+dnl *                                                                         *
+dnl * You should have received a copy of the GNU Lesser General Public        *
+dnl * License along with this library; if not, write to the Free Software     *
+dnl * Foundation, Inc., 51 Franklin Street, Fifth Floor,                      *
+dnl * Boston, MA  02110-1301  USA                                             *
+dnl *                                                                         *
+dnl * CLooG, the Chunky Loop Generator                                        *
+dnl * Written by Cedric Bastoul, Cedric.Bastoul@xxxxxxxx                      *
+dnl *                                                                         *
+dnl
***************************************************************************/
+
+m4_define([version_major], [0])
+m4_define([version_minor], [18])
+m4_define([version_revision], [0])
+
+AC_PREREQ(2.53)
+AC_INIT([cloog], [version_major.version_minor.version_revision],
+       [cloog-development@xxxxxxxxxxxxxxxx])
+AC_CONFIG_SRCDIR(source/cloog.c)
+AC_CONFIG_AUX_DIR(autoconf)
+AC_CONFIG_MACRO_DIR([m4])
+
+VERSION_MAJOR=version_major
+VERSION_MINOR=version_minor
+VERSION_REVISION=version_revision
+AC_SUBST(versioninfo)
+versioninfo=4:0:0
+
+AM_INIT_AUTOMAKE([foreign])
+m4_ifdef([AM_SILENT_RULES],[AM_SILENT_RULES([yes])])
+
+dnl /**************************************************************************
+dnl  *                              Checking                                  *
+dnl
**************************************************************************/
+
+dnl Checks for programs.
+AC_PROG_CC
+AC_PROG_LN_S
+AC_PROG_MAKE_SET
+AC_CHECK_PROG(CD, cd)
+dnl Configure needs an empty install.sh file with this, i HATE that...
+AC_PROG_INSTALL
+AC_PROG_LIBTOOL
+AC_CHECK_PROG(TEXI2DVI, texi2dvi, texi2dvi, [])
+AM_CONDITIONAL(HAVE_TEXI2DVI, test -n "$TEXI2DVI") + +AX_CC_MAXOPT +AC_SUBST(CFLAGS_WARN) +AX_CFLAGS_WARN_ALL(CFLAGS_WARN) + +dnl Checks for typedefs, structures, and compiler characteristics. +AC_C_CONST +AC_TYPE_SIZE_T + + + +dnl Checks for header files. +AC_HEADER_STDC + + +dnl Checks for library functions. +AC_CHECK_FUNCS(strtol) + + +dnl /************************************************************************** +dnl * Option setting * +dnl **************************************************************************/ + +AC_CHECK_FUNCS([getrusage], + [AC_DEFINE([CLOOG_RUSAGE], [], [Print time required to generate code])]) + +AX_SUBMODULE(isl,no|system|build|bundled,bundled) +BITS="gmp" + +dnl /************************************************************************** +dnl * Where is GMP? * +dnl **************************************************************************/ + +AX_SUBMODULE(gmp,system|build,system) + +need_get_memory_functions=false +case "$with_gmp" in
+build)
+    CPPFLAGS="-I$with_gmp_builddir$CPPFLAGS"
+    LDFLAGS="-L$with_gmp_builddir/$lt_cv_objdir $LDFLAGS" + ;; +system) + if test "x$with_gmp_prefix" != "x"; then
+       CPPFLAGS="-I$with_gmp_prefix/include$CPPFLAGS"
+    fi
+
+    if test "$with_gmp_exec_prefix" != "yes" ; then + LDFLAGS="-L$with_gmp_exec_prefix/lib $LDFLAGS" + fi + ;; +esac +case "$with_gmp" in
+build|system)
+                    [],
+    AC_CHECK_LIB(gmp,
+                 __gmpz_init,
+                 [LIBS="$LIBS -lgmp"], + [AC_MSG_ERROR(Can't find gmp library.)]) + AC_CHECK_DECLS(mp_get_memory_functions,[],[ + need_get_memory_functions=true + ],[#include <gmp.h>]) + ;; +esac +AM_CONDITIONAL(NEED_GET_MEMORY_FUNCTIONS, + test x$need_get_memory_functions = xtrue)
+
+dnl /**************************************************************************
+dnl  *                          Where is isl?                                 *
+dnl
**************************************************************************/
+
+AC_SUBST(ISL_CPPFLAGS)
+AC_SUBST(ISL_LDFLAGS)
+AC_SUBST(ISL_LIBS)
+case "$with_isl" in +bundled) + ISL_CPPFLAGS="-I$srcdir/isl/include -Iisl/include"
+       ;;
+build)
+       ISL_CPPFLAGS="-I$isl_srcdir/include -I$with_isl_builddir/include"
+       ISL_LIBS="$with_isl_builddir/libisl.la" + ;; +system) + if test "x$with_isl_prefix" != "x"; then
+               ISL_CPPFLAGS="-I$with_isl_prefix/include" + fi + if test "x$with_isl_exec_prefix" != "x"; then
+               ISL_LDFLAGS="-L$with_isl_exec_prefix/lib" + fi + ISL_LIBS="-lisl" +esac +AM_CONDITIONAL(BUNDLED_ISL, test$with_isl = bundled)
+AM_CONDITIONAL(NO_ISL, test $with_isl = no) + + +dnl /************************************************************************** +dnl * Where is the OpenScop Library? * +dnl **************************************************************************/ + +AX_SUBMODULE(osl,no|system|build|bundled,no) +osl_flag="OSL_SUPPORT" + +AC_SUBST(OSL_CPPFLAGS) +AC_SUBST(OSL_LDFLAGS) +AC_SUBST(OSL_LIBS) +case "$with_osl" in
+bundled)
+       OSL_CPPFLAGS="-D$osl_flag -I$srcdir/osl/include -Iosl/include"
+       ;;
+build)
+       OSL_CPPFLAGS="-D$osl_flag -I$osl_srcdir/include
-I$with_osl_builddir/include" + OSL_LIBS="$with_osl_builddir/libosl.la"
+       ;;
+system)
+       if test "x$with_osl_prefix" != "x"; then + OSL_CPPFLAGS="-D$osl_flag -I$with_osl_prefix/include" + fi + if test "x$with_osl_exec_prefix" != "x"; then
+               OSL_LDFLAGS="-L$with_osl_exec_prefix/lib" + fi + OSL_LIBS="-losl" +esac +AM_CONDITIONAL(BUNDLED_OSL, test$with_osl = bundled)
+AM_CONDITIONAL(NO_OSL, test $with_osl = no) + + +AC_DEFINE([CLOOG_INT_GMP], 1, [Use arbitrary precision integers]) + +AC_SUBST(GIT_INDEX) +if test -f$srcdir/.git/HEAD; then
+       GIT_INDEX="\$(top_srcdir)/.git/index" +fi + + +dnl /************************************************************************** +dnl * Substitutions * +dnl **************************************************************************/ + + +dnl Substitutions to do in Makefile.in. +AC_SUBST(CC) +AC_SUBST(LN_S) + +AC_SUBST(prefix) +AC_SUBST(exec_prefix) +AC_SUBST(INSTALL) + +AC_SUBST(BITS) + +AC_SUBST(VERSION_MAJOR) +AC_SUBST(VERSION_MINOR) +AC_SUBST(VERSION_REVISION) + +PACKAGE_NAME="cloog-isl" +PACKAGE_CFLAGS="-DCLOOG_INT_GMP=1" +AX_CREATE_PKGCONFIG_INFO + +AC_CONFIG_FILES(Makefile test/Makefile) +AC_CONFIG_FILES(autoconf/Doxyfile) +AC_CONFIG_FILES(doc/Makefile) +AC_CONFIG_FILES(source/version.c) +AC_CONFIG_FILES(include/cloog/version.h) +AC_CONFIG_FILES([genversion.sh], [chmod +x genversion.sh]) +AC_CONFIG_COMMANDS([version.h], + [echo '#define CLOOG_HEAD "'./genversion.sh'"' > version.h]) +AC_CONFIG_COMMANDS([doc/gitversion.texi], + [echo '@set VERSION './genversion.sh'' > doc/gitversion.texi]) +if test$with_isl = bundled; then
+       AC_CONFIG_SUBDIRS(isl)
+fi
+if test $with_osl = bundled; then + AC_CONFIG_SUBDIRS(osl) +fi +AC_CONFIG_COMMANDS_POST([ + ac_configure_args="$ac_configure_args $cloog_configure_args" +]) +AC_OUTPUT + + +echo " /*-----------------------------------------------*" +echo " * CLooG configuration is OK *" +echo " *-----------------------------------------------*/" +echo "It appears that your system is OK to start CLooG compilation. You need" +echo "now to type \"make\". After compilation, you should check CLooG by typing" +echo "\"make check\". If no problem occur, you can type \"make uninstall\" if" +echo "you are upgrading an old version. Lastly type \"make install\" to install" +echo "CLooG on your system (log as root if necessary)." diff --git a/cloog/doc/Makefile.am b/cloog/doc/Makefile.am new file mode 100644 index 0000000..160dfd1 --- /dev/null +++ b/cloog/doc/Makefile.am @@ -0,0 +1,7 @@ +if HAVE_TEXI2DVI +cloog.pdf: cloog.texi gitversion.texi +$(TEXI2DVI) --pdf $< +endif + +gitversion.texi: @GIT_INDEX@ + echo '@set VERSION '$(top_builddir)/genversion.sh'' > \$@
new file mode 100644
index 0000000..03e9465
--- /dev/null
@@ -0,0 +1,18 @@
+still to do before
+0.14.0 - dumping functions
+       - backtrack only to remove ifs
+       - update documentation
+       - configure for GMP and Solaris
+
+0.14.1 - remove the constraint that all scattering functions must have the same
+         dimensionality and use the new liberty degrees to generate better
codes
+         (e.g. continue loop fusion only when the stride is the same...)
+       - if-hoisting instead of backtracking by option
+
+0.14.2 clean loop during generation (haircut and never_integral)
+
+0.14.3 allow non-integral scattering (easy: see PACT paper)
+
+...
+
+1.0.0  Omega-like input.

[ *** diff truncated: 1284912 lines dropped *** ]



### Other related posts:

• » [haiku-commits] buildtools: btrev43052 - ppl/doc cloog/test ppl cloog/isl ppl/src - korli