Intel Parallel Studio For Fortran
2021年12月17日Download here: http://gg.gg/xa3bs
This page provides the current Release Notes for the Debug Solutions from Intel® Parallel Studio XE 2020 Composer Edition for Fortran Linux*, Windows* and macOS* products. To get product updates, log in to the Intel® Software Development Products Registration Center. For questions or technical support, visit Intel® Software Products Support.
*Intel Parallel Studio Xe 2019 For Fortran
*Intel Parallel Studio Xe 2017 For Fortran
*Intel Parallel Studio Xe 2020 For Fortran
*Intel Parallel Studio Xe 2019 For Fortran
*Intel Parallel Studio Fortran Linux
*Intel Parallel Studio Fortran Student
*Intel Parallel Studio Fortran CompilerChange History
*I have installed Intel Parallel Studio XE which includes the iFort compiler and Microsoft Visual Studio. During the installation of Intel Parallel Studio XE, it showed a message saying it’s now integrated with Visual Studio 2019 but when I try to create a new project in Visual Studio, it does not show an option for Intel Fortran Compiler, so I.
*MKL pardiso on Intel Parallel studio Fortran. Ask Question Asked 1 year, 3 months ago. Active 1 year, 3 months ago. Viewed 136 times 0 Trying to make work MKLPardiso.
*Intel ® Parallel Studio XE for Windows, Linux or MacOS Three editions based on your development needs: Composer Edition (BUILD) Intel® Parallel Studio XE 2019 Composer Edition includes industry-leading C and Fortran compilers, performance libraries, standards-based parallel models, and performance-optimized Python. Build fast code, faster.
This section highlights important from the previous product version and changes in product updates. Changes since Intel® Parallel Studio XE 2019 Composer Edition
*Support for GNU* Project Debugger (GDB) 8.3
*Updated to include Python* 3 Product Contents
*Linux*:
*GNU* Project Debugger (GDB) 8.3: Command line for CPU, and Eclipse* IDE plugin.
*macOS*:
*GNU Project Debugger (GDB) 8.3: Command line for CPU only.
Intel Parallel Studio XE for Educators Faculty and PhD Students can download a free version of the Intel C and Fortran compilers by registering here. After filling out a short questionnaire, you will receive a software license key within two business days.GNU* GDB
This section summarizes the changes, new features, customizations and known issues related to the GNU* GDB provided with Intel® Parallel Studio XE 2020 Composer Edition.Intel Parallel Studio Xe 2019 For FortranFeatures
GNU GDB provided with Intel® Parallel Studio XE 2020 Composer Edition and above is based on GDB 8.3 with additional enhancements provided by Intel. In addition to features found in GDB 8.3, there are several other new features:
*Support for Intel® Transactional Synchronization Extensions (Intel® TSX) (Linux* and macOS*).
*Data Race Detection (pdbx): Detect and locate data races for applications threaded using POSIX* thread (pthread) or OpenMP* models.
*Open Multi-Processing Debugging (OpenMP): Visualize additional information about OpenMP* tasks, locks, barriers and others.
*PTWRITE for Intel® Processor Trace (Intel® PT): Customized printing of PTWRITE payloads in the instruction history and function-call history.
*Intel® Control-Flow Enforcement Technology (Intel® CET): New commands to display the shadow stack backtrace and CET status information.
All features are available for Linux*, but only Intel® TSX is supported for macOS*.Using GNU* GDB
GNU* GDB provided with Intel® Parallel Studio XE 2020 Composer Edition comes in different versions:
*IA-32/Intel® 64 debugger: Debug applications natively on IA-32 or Intel® 64 systems with gdb-ia on the command line.
A standard Eclipse* IDE can be used for this as well if a graphical user interface is desired.Documentation
The documentation for the provided GNU GDB can be found here:
*Getting Started with Debugging with Intel® Parallel Studio XE for Windows* OS Known Issues and ChangesIntel Parallel Studio Xe 2017 For FortranLinux:
No known issues.macOS*:
macOS* 10.15 introduced new security features that affect debugging. To enable debugging on a system with System Integrity Protection* and Hardened Runtime*, the program or process that is being debugged needs to run with the com.apple.security.get-task-allow entitlement. This entitlement can be given to the program during the digital signing process and is typically added by Xcode* automatically for Debug builds. For more details on how to sign your binaries with com.apple.security.get-task-allow, please refer to Apple* documentation. If you encounter the error message “During startup program terminated with Signal ?, Unknown Signal”, please retry your previous command. After some tries your debugging session should start and work as expected. This is a known issue we are planning to resolve in a future update. Another known issue is the warning message: “warning: unhandled dyld version (16)”, which can safely be ignored. This warning will be resolved in a future update.Fortran Expression Evaluator (FEE) for Debugging Fortran Applications with Microsoft Visual Studio*
Fortran Expression Evaluator (FEE) is a plug-in for Microsoft Visual Studio* that is installed with Intel® Visual Fortran Compiler. It extends the standard debugger in Microsoft Visual Studio* IDE by handling Fortran expressions. There is no other change in usability.Known Issues and LimitationsIntel Parallel Studio Xe 2020 For FortranConditional breakpoints limited
Conditional breakpoints that contain expressions with allocatable variables are not supported for Microsoft Visual Studio 2012* or later.Debugging mixed language programs with Fortran does not work
To enable debugging Fortran code called from a .NET managed code application in Visual Studio 2012 or later, unset the following configuration:Menu Tools > Options, under section Debugging > General, clear the Managed C++ Compatibility Mode or Use Managed Compatibility Mode check box
For any managed code application, one must also check the project property Debug > Enable unmanaged code debugging.Native edit and continue
With Microsoft Visual Studio 2015*, Fortran debugging of mixed code applications is enabled if native edit and continue is enabled for the C/C++ part of the code. In earlier versions this is not supported.Attributions
This product includes software developed at: GDB – The GNU* Project Debugger Copyright Free Software Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA. This program is free software; you can redistribute it and/or modify it under the terms and conditions of the GNU General Public License, version 2, as published by the Free Software Foundation. This program is distributed in the hope 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., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.Intel Parallel Studio Xe 2019 For FortranGNU* Free Documentation License
Version 1.3, 3 November 2008 Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document ’free’ in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of ’copyleft’, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The ’Document’, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as ’you’. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A ’Modified Version’ of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A ’Secondary Section’ is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The ’Invariant Sections’ are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The ’Cover Texts’ are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A ’Transparent’ copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not ’Transparent’ is called ’Opaque’. Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The ’Title Page’ means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, ’Title Page’ means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text. The ’publisher’ means any person or entity that distributes copies of the Document to the public. A section ’Entitled XYZ’ means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as ’Acknowledgements’, ’Dedications’, ’Endorsements’, or ’History’.) To ’Preserve the Title’ of such a section when you modify the Document means that it remains a section ’Entitled XYZ’ according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled ’History’, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled ’History’ in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the ’History’ section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled ’Acknowledgements’ or ’Dedications’, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text a
https://diarynote.indered.space
This page provides the current Release Notes for the Debug Solutions from Intel® Parallel Studio XE 2020 Composer Edition for Fortran Linux*, Windows* and macOS* products. To get product updates, log in to the Intel® Software Development Products Registration Center. For questions or technical support, visit Intel® Software Products Support.
*Intel Parallel Studio Xe 2019 For Fortran
*Intel Parallel Studio Xe 2017 For Fortran
*Intel Parallel Studio Xe 2020 For Fortran
*Intel Parallel Studio Xe 2019 For Fortran
*Intel Parallel Studio Fortran Linux
*Intel Parallel Studio Fortran Student
*Intel Parallel Studio Fortran CompilerChange History
*I have installed Intel Parallel Studio XE which includes the iFort compiler and Microsoft Visual Studio. During the installation of Intel Parallel Studio XE, it showed a message saying it’s now integrated with Visual Studio 2019 but when I try to create a new project in Visual Studio, it does not show an option for Intel Fortran Compiler, so I.
*MKL pardiso on Intel Parallel studio Fortran. Ask Question Asked 1 year, 3 months ago. Active 1 year, 3 months ago. Viewed 136 times 0 Trying to make work MKLPardiso.
*Intel ® Parallel Studio XE for Windows, Linux or MacOS Three editions based on your development needs: Composer Edition (BUILD) Intel® Parallel Studio XE 2019 Composer Edition includes industry-leading C and Fortran compilers, performance libraries, standards-based parallel models, and performance-optimized Python. Build fast code, faster.
This section highlights important from the previous product version and changes in product updates. Changes since Intel® Parallel Studio XE 2019 Composer Edition
*Support for GNU* Project Debugger (GDB) 8.3
*Updated to include Python* 3 Product Contents
*Linux*:
*GNU* Project Debugger (GDB) 8.3: Command line for CPU, and Eclipse* IDE plugin.
*macOS*:
*GNU Project Debugger (GDB) 8.3: Command line for CPU only.
Intel Parallel Studio XE for Educators Faculty and PhD Students can download a free version of the Intel C and Fortran compilers by registering here. After filling out a short questionnaire, you will receive a software license key within two business days.GNU* GDB
This section summarizes the changes, new features, customizations and known issues related to the GNU* GDB provided with Intel® Parallel Studio XE 2020 Composer Edition.Intel Parallel Studio Xe 2019 For FortranFeatures
GNU GDB provided with Intel® Parallel Studio XE 2020 Composer Edition and above is based on GDB 8.3 with additional enhancements provided by Intel. In addition to features found in GDB 8.3, there are several other new features:
*Support for Intel® Transactional Synchronization Extensions (Intel® TSX) (Linux* and macOS*).
*Data Race Detection (pdbx): Detect and locate data races for applications threaded using POSIX* thread (pthread) or OpenMP* models.
*Open Multi-Processing Debugging (OpenMP): Visualize additional information about OpenMP* tasks, locks, barriers and others.
*PTWRITE for Intel® Processor Trace (Intel® PT): Customized printing of PTWRITE payloads in the instruction history and function-call history.
*Intel® Control-Flow Enforcement Technology (Intel® CET): New commands to display the shadow stack backtrace and CET status information.
All features are available for Linux*, but only Intel® TSX is supported for macOS*.Using GNU* GDB
GNU* GDB provided with Intel® Parallel Studio XE 2020 Composer Edition comes in different versions:
*IA-32/Intel® 64 debugger: Debug applications natively on IA-32 or Intel® 64 systems with gdb-ia on the command line.
A standard Eclipse* IDE can be used for this as well if a graphical user interface is desired.Documentation
The documentation for the provided GNU GDB can be found here:
*Getting Started with Debugging with Intel® Parallel Studio XE for Windows* OS Known Issues and ChangesIntel Parallel Studio Xe 2017 For FortranLinux:
No known issues.macOS*:
macOS* 10.15 introduced new security features that affect debugging. To enable debugging on a system with System Integrity Protection* and Hardened Runtime*, the program or process that is being debugged needs to run with the com.apple.security.get-task-allow entitlement. This entitlement can be given to the program during the digital signing process and is typically added by Xcode* automatically for Debug builds. For more details on how to sign your binaries with com.apple.security.get-task-allow, please refer to Apple* documentation. If you encounter the error message “During startup program terminated with Signal ?, Unknown Signal”, please retry your previous command. After some tries your debugging session should start and work as expected. This is a known issue we are planning to resolve in a future update. Another known issue is the warning message: “warning: unhandled dyld version (16)”, which can safely be ignored. This warning will be resolved in a future update.Fortran Expression Evaluator (FEE) for Debugging Fortran Applications with Microsoft Visual Studio*
Fortran Expression Evaluator (FEE) is a plug-in for Microsoft Visual Studio* that is installed with Intel® Visual Fortran Compiler. It extends the standard debugger in Microsoft Visual Studio* IDE by handling Fortran expressions. There is no other change in usability.Known Issues and LimitationsIntel Parallel Studio Xe 2020 For FortranConditional breakpoints limited
Conditional breakpoints that contain expressions with allocatable variables are not supported for Microsoft Visual Studio 2012* or later.Debugging mixed language programs with Fortran does not work
To enable debugging Fortran code called from a .NET managed code application in Visual Studio 2012 or later, unset the following configuration:Menu Tools > Options, under section Debugging > General, clear the Managed C++ Compatibility Mode or Use Managed Compatibility Mode check box
For any managed code application, one must also check the project property Debug > Enable unmanaged code debugging.Native edit and continue
With Microsoft Visual Studio 2015*, Fortran debugging of mixed code applications is enabled if native edit and continue is enabled for the C/C++ part of the code. In earlier versions this is not supported.Attributions
This product includes software developed at: GDB – The GNU* Project Debugger Copyright Free Software Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA. This program is free software; you can redistribute it and/or modify it under the terms and conditions of the GNU General Public License, version 2, as published by the Free Software Foundation. This program is distributed in the hope 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., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.Intel Parallel Studio Xe 2019 For FortranGNU* Free Documentation License
Version 1.3, 3 November 2008 Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document ’free’ in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of ’copyleft’, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The ’Document’, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as ’you’. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A ’Modified Version’ of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A ’Secondary Section’ is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The ’Invariant Sections’ are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The ’Cover Texts’ are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A ’Transparent’ copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not ’Transparent’ is called ’Opaque’. Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The ’Title Page’ means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, ’Title Page’ means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text. The ’publisher’ means any person or entity that distributes copies of the Document to the public. A section ’Entitled XYZ’ means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as ’Acknowledgements’, ’Dedications’, ’Endorsements’, or ’History’.) To ’Preserve the Title’ of such a section when you modify the Document means that it remains a section ’Entitled XYZ’ according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled ’History’, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled ’History’ in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the ’History’ section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled ’Acknowledgements’ or ’Dedications’, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text a
https://diarynote.indered.space
コメント