--- /dev/null
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, 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 or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+\f
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+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 give any other recipients of the Program a copy of this License
+along with the Program.
+
+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 Program or any portion
+of it, thus forming a work based on the Program, 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) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+\f
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+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 Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+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 Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) 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; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, 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 executable. However, as a
+special exception, the source code 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.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+\f
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. 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 Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program 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 to
+this License.
+
+ 7. 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
+otherwise) that contradict the conditions of this License, they do not
+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 Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program 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 Program.
+
+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
+implemented by public license practices. Many people have made
+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.
+\f
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add 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.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the 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 Program
+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 Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, 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
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "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 PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. 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 PROGRAM 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 PROGRAM (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 PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+\f
+ Appendix: How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ 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 of the License, 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; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
--- /dev/null
+1997-06-20
+
+This directory contains the version 0.5.21 release of the GNU Fortran
+compiler. The GNU Fortran compiler is free software. See the file
+COPYING.g77 for copying permission.
+
+* IMPORTANT: Things you _must_ do are marked with a * at the beginning of
+ the line in this file!!!
+
+This README is for GNU Fortran, and describes the files in the f/
+directory. The f/ directory is intended to be a subdirectory of a
+gcc source tree. These directories are referred to below as gcc/,
+which is the top-level directory containing the gcc back end, the
+gcc C front end, and other non-Fortran files, and gcc/f/, which
+contains all of the Fortran files.
+
+* To build GNU Fortran, you must have a source distribution of gcc
+ version 2.7.2.2. Do not attempt to use any other version
+ of gcc, because this version of g77 is designed to work only with
+ gcc version 2.7.2.2.
+
+* Note that you must have source copies of these gcc distributions!!
+ You cannot build g77 just using binaries of gcc. Also, unless you
+ are an expert, avoid using any distribution of gcc not identical to
+ the one distributed by the FSF -- for example, using a special version
+ modified to produce better code for the Pentium (sometimes labeled
+ gcc-i2.6.3 -- note the `i') will not work with this distribution of g77.
+
+If you have just unpacked the g77 distribution, before proceeding,
+you must merge the contents of the g77 distribution with the appropriate
+gcc distribution on your system before proceeding.
+
+* Read and follow the instructions in g77-0.5.21/f/INSTALL that
+ explain how to merge a g77 source directory into a gcc source
+ directory. You can use Info to read the same installation
+ instructions via:
+
+ info -f g77-0.5.21/f/g77.info -n Unpacking
+
+The resulting directory layout includes the following, where gcc/ might be
+a link to, for example, gcc-2.7.2.2/:
+
+ gcc/ Non-Fortran files in gcc (not part of g77*.tar)
+ gcc/README.g77 This file
+ gcc/f/ GNU Fortran front end
+ gcc/f/gbe/ Patches required for gcc back end versions
+ gcc/f/runtime/ libf2c configuration and f2c.h file generation
+ gcc/f/runtime/libF77/ Non-I/O portion of libf2c
+ gcc/f/runtime/libI77/ I/O portion of libf2c
+ gcc/f/runtime/libU77/ Additional interfaces to libc for libf2c
+
+gcc/f/ as a whole contains the program GNU Fortran (g77), plus a portion
+of the separate program f2c, which is in gcc/f/runtime. NOTE: The f2c
+code is not part of the program g77, just distributed with it.
+
+This directory is named gcc/f/ because it, along with its contents, is
+designed to be a subdirectory of a GNU CC (gcc) development directory. I.e.
+when a gcc distribution is unpacked into a directory (named gcc/ for
+example), it typically contains subdirectories like gcc/config/ and
+gcc/cp/. The latter is the subdirectory for the GNU C++ (g++) program.
+
+Similarly, the g77 directory f/ is designed to be placed in gcc/ so that
+it becomes the subdirectory gcc/f/. g77 is distributed as g77-someversion/f/
+so that unpacking the g77 distribution is done in the normal GNU way,
+resulting in a directory having the version number in the name. However,
+to build g77, the g77 distribution must be merged with an appropriate gcc
+distribution, normally in a gcc directory, before configuring, building,
+and installing g77.
+
+Applying g77 patches in the form of .diff files is done by typing
+"patch -p1 -d gcc" (where gcc/f/ is the active version). That is,
+g77 patches are distributed in the same form, and at the same directory
+level, as patches to the gcc distribution.
+
+gcc/f/ has text files that document the Fortran compiler, source
+files for the GNU Fortran Front End (FFE), and some other stuff.
+
+gcc/f/gbe/ has patch files for various versions of gcc, primarily
+needed to patch the GNU compiler Back End (GBE) to fix and improve it
+for use with g77. If a patch file exists for the version of gcc you
+want to build along with g77, you MUST apply the patch before building
+g77 with that version or g77 will not build or work properly.*
+
+* Read gcc/f/gbe/README for more information.
+
+gcc/f/runtime/ contains the run-time libraries for the f2c program, also used
+by g77, and referred to as libf2c (though libf2c is really a combination of
+two distinct libraries, libF77 and libI77 -- in g77, this distinction is
+not made, and, further, Dave Love's implementation of libU77 is added
+to the mix). This separate subdirectory is not part of the program g77, just
+distributed with it. Some new files have been added to this subdirectory
+and some minor changes made to the files contained therein, to fix some
+bugs and facilitate automatic configuration, building, and installation of
+libf2c for use by g77 users. See gcc/f/runtime/README for more information.
+
+gcc/f/BUGS lists some important bugs known to be in g77. Or:
+
+ info -f gcc/f/g77.info -n "Actual Bugs"
+
+gcc/f/ChangeLog lists recent changes to g77 internals.
+
+gcc/f/INSTALL describes how to build and install GNU Fortran. Or:
+
+ info -f gcc/f/g77.info -n Installation
+
+gcc/f/NEWS contains the per-release changes (not just user-visible ones
+seen in gcc/f/DOC) listed in the ~fortran/.plan file. Or:
+
+ info -f gcc/f/g77.info -n News
+
+* Read gcc/f/BUGS, gcc/f/INSTALL, and gcc/f/NEWS at the very least!
+ All users of g77 (not just installers) should read gcc/f/g77.info*
+ as well, using the "more" command if the "info" command is
+ unavailable or they aren't accustomed to using it.
+
+If you want to get into the FFE code, which lives entirely in gcc/f/, here
+are a few clues. The file g77.c is the stand-alone source file for the
+`g77' command driver only -- this just invokes the `gcc' command, so it has
+nothing to do with the rest of the code in g77. Most of the code
+ends up in an executable named `f771', which does the actual compiling,
+so it has the FFE merged with the gcc back end.
+
+The file parse.c is the source file for main() for a stand-alone FFE and
+yyparse() for f771. (Stand-alone building of the FFE doesn't work these days.)
+The file top.c contains the top-level FFE function ffe_file and it (along
+with top.h) define all ffe_[a-z].*, ffe[A-Z].*, and FFE_[A-Za-z].* symbols.
+The file fini.c is a main() program that is used when building the FFE to
+generate C header and source files for recognizing keywords. The files
+malloc.c and malloc.h comprise a memory manager that defines all
+malloc_[a-z].*, malloc[A-Z].*, and MALLOC_[A-Za-z].* symbols. All other
+modules named <xyz> are comprised of all files named <xyz>*.<ext> and
+define all ffe<xyz>_[a-z].*, ffe<xyz>[A-Z].*, and FFE<XYZ>_[A-Za-z].* symbols.
+If you understand all this, congratulations -- it's easier for me to remember
+how it works than to type in these grep patterns (such as they are). But it
+does make it easy to find where a symbol is defined -- for example,
+the symbol "ffexyz_set_something" would be defined in xyz.h and implemented
+there (if it's a macro) or in xyz.c.
+
+The "porting" files of note currently are: proj.h, which defines the
+"language" used by all the other source files (the language being
+Standard C plus some useful things like ARRAY_SIZE and such) -- change
+this file when you find your system doesn't properly define a Standard C
+macro or function, for example; target.h and target.c, which describe
+the target machine in terms of what data types are supported, how they are
+denoted (what C type does an INTEGER*8 map to, for example), how to convert
+between them, and so on (though as of 0.5.3, more and more of this information
+is being dynamically configured by ffecom_init_0); com.h and com.c, which
+interface to the target back end (currently only FFE stand-alone and the GBE);
+ste.c, which contains code for implementing recognized executable statements
+in the target back end (again currently either FFE or GBE); src.h and src.c,
+which describe information on the format(s) of source files (like whether
+they are never to be processed as case-insensitive with regard to Fortran
+keywords); and proj.c, which contains whatever code is needed to support
+the language defined by proj.h.
+
+If you want to debug the f771 executable, for example if it crashes,
+note that the global variables "lineno" and "input_filename" are set
+to reflect the current line being read by the lexer during the first-pass
+analysis of a program unit and to reflect the current line being
+processed during the second-pass compilation of a program unit. If
+an invocation of the function ffestd_exec_end() is on the stack,
+the compiler is in the second pass, otherwise it is in the first.
+(This information might help you reduce a test case and/or work around
+a bug in g77 until a fix is available.)
+
+Any questions or comments on these topics, email fortran@gnu.ai.mit.edu.
projects / platform / upstream / linaro-gcc.git / commitdiff