I replaced and verified http:// links for various domains.
gcc/ada/ChangeLog:
* doc/share/gnu_free_documentation_license.rst: Replace http:// with https.
* gnat-style.texi: Likewise.
* gnat_rm.texi: Likewise.
* gnat_ugn.texi: Likewise.
gcc/d/ChangeLog:
* gdc.texi: Replace http:// with https.
gcc/ChangeLog:
* doc/contrib.texi: Replace http:// with https.
* doc/contribute.texi: Likewise.
* doc/extend.texi: Likewise.
* doc/gccint.texi: Likewise.
* doc/gnu.texi: Likewise.
* doc/implement-c.texi: Likewise.
* doc/implement-cxx.texi: Likewise.
* doc/include/fdl.texi: Likewise.
* doc/include/gpl_v3.texi: Likewise.
* doc/install.texi: Likewise.
* doc/invoke.texi: Likewise.
* doc/passes.texi: Likewise.
* doc/service.texi: Likewise.
* doc/sourcebuild.texi: Likewise.
* doc/standards.texi: Likewise.
gcc/fortran/ChangeLog:
* gfortran.texi: Replace http:// with https.
* intrinsic.texi: Likewise.
gcc/go/ChangeLog:
* gccgo.texi: Replace http:// with https.
gcc/jit/ChangeLog:
* docs/_build/texinfo/libgccjit.texi: Replace http:// with https.
* docs/cp/index.rst: Likewise.
* docs/cp/intro/index.rst: Likewise.
* docs/cp/intro/tutorial01.rst: Likewise.
* docs/cp/intro/tutorial02.rst: Likewise.
* docs/cp/intro/tutorial03.rst: Likewise.
* docs/cp/intro/tutorial04.rst: Likewise.
* docs/cp/topics/asm.rst: Likewise.
* docs/cp/topics/compilation.rst: Likewise.
* docs/cp/topics/contexts.rst: Likewise.
* docs/cp/topics/expressions.rst: Likewise.
* docs/cp/topics/functions.rst: Likewise.
* docs/cp/topics/index.rst: Likewise.
* docs/cp/topics/locations.rst: Likewise.
* docs/cp/topics/objects.rst: Likewise.
* docs/cp/topics/types.rst: Likewise.
* docs/index.rst: Likewise.
* docs/internals/index.rst: Likewise.
* docs/intro/index.rst: Likewise.
* docs/intro/tutorial01.rst: Likewise.
* docs/intro/tutorial02.rst: Likewise.
* docs/intro/tutorial03.rst: Likewise.
* docs/intro/tutorial04.rst: Likewise.
* docs/intro/tutorial05.rst: Likewise.
* docs/topics/asm.rst: Likewise.
* docs/topics/compatibility.rst: Likewise.
* docs/topics/compilation.rst: Likewise.
* docs/topics/contexts.rst: Likewise.
* docs/topics/expressions.rst: Likewise.
* docs/topics/function-pointers.rst: Likewise.
* docs/topics/functions.rst: Likewise.
* docs/topics/index.rst: Likewise.
* docs/topics/locations.rst: Likewise.
* docs/topics/objects.rst: Likewise.
* docs/topics/performance.rst: Likewise.
* docs/topics/types.rst: Likewise.
Version 1.3, 3 November 2008
Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
-http://fsf.org/
+https://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
of the GNU Free Documentation 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. See
-http://www.gnu.org/copyleft/.
+https://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
Version 1.3, 3 November 2008
Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
-@indicateurl{http://fsf.org/}
+@indicateurl{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
of the GNU Free Documentation 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. See
-@indicateurl{http://www.gnu.org/copyleft/}.
+@indicateurl{https://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
Version 1.3, 3 November 2008
Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
-@indicateurl{http://fsf.org/}
+@indicateurl{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
of the GNU Free Documentation 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. See
-@indicateurl{http://www.gnu.org/copyleft/}.
+@indicateurl{https://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
Version 1.3, 3 November 2008
Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc
-@indicateurl{http://fsf.org/}
+@indicateurl{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
of the GNU Free Documentation 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. See
-@indicateurl{http://www.gnu.org/copyleft/}.
+@indicateurl{https://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
@item all
Turns on all upcoming D language features.
@item dip1000
-Implements @uref{http://wiki.dlang.org/DIP1000} (Scoped pointers).
+Implements @uref{https://wiki.dlang.org/DIP1000} (Scoped pointers).
@item dip1008
-Implements @uref{http://wiki.dlang.org/DIP1008} (Allow exceptions in
+Implements @uref{https://wiki.dlang.org/DIP1008} (Allow exceptions in
@code{@@nogc} code).
@item dip1021
-Implements @uref{http://wiki.dlang.org/DIP1021} (Mutable function arguments).
+Implements @uref{https://wiki.dlang.org/DIP1021} (Mutable function arguments).
@item dip25
-Implements @uref{http://wiki.dlang.org/DIP25} (Sealed references).
+Implements @uref{https://wiki.dlang.org/DIP25} (Sealed references).
@item dtorfields
Turns on generation for destructing fields of partially constructed objects.
@item fieldwise
@item all
Turns off all revertable D language features.
@item dip25
-Reverts @uref{http://wiki.dlang.org/DIP25} (Sealed references).
+Reverts @uref{https://wiki.dlang.org/DIP25} (Sealed references).
@item dtorfields
Turns off generation for destructing fields of partially constructed objects.
@item markdown
Branko Cibej for more warning contributions.
@item
-The @uref{http://www.gnu.org/software/classpath/,,GNU Classpath project}
+The @uref{https://www.gnu.org/software/classpath/,,GNU Classpath project}
for all of their merged runtime code.
@item
If you would like to help pretest GCC releases to assure they work well,
current development sources are available via Git (see
-@uref{http://gcc.gnu.org/git.html}). Source and binary snapshots are
-also available for FTP; see @uref{http://gcc.gnu.org/snapshots.html}.
+@uref{https://gcc.gnu.org/git.html}). Source and binary snapshots are
+also available for FTP; see @uref{https://gcc.gnu.org/snapshots.html}.
If you would like to work on improvements to GCC, please read the
advice at these URLs:
@smallexample
-@uref{http://gcc.gnu.org/contribute.html}
-@uref{http://gcc.gnu.org/contributewhy.html}
+@uref{https://gcc.gnu.org/contribute.html}
+@uref{https://gcc.gnu.org/contributewhy.html}
@end smallexample
@noindent
for information on how to make useful contributions and avoid
duplication of effort. Suggested projects are listed at
-@uref{http://gcc.gnu.org/projects/}.
+@uref{https://gcc.gnu.org/projects/}.
There are 6 different memory orders that can be specified. These map
to the C++11 memory orders with the same names, see the C++11 standard
-or the @uref{http://gcc.gnu.org/wiki/Atomic/GCCMM/AtomicSync,GCC wiki
+or the @uref{https://gcc.gnu.org/wiki/Atomic/GCCMM/AtomicSync,GCC wiki
on atomic synchronization} for detailed definitions. Individual
targets may also support additional memory orders for use on specific
architectures. Refer to the target documentation for details of
different target string. Function foo is called or a pointer to it is
taken just like a regular function. GCC takes care of doing the
dispatching to call the right version at runtime. Refer to the
-@uref{http://gcc.gnu.org/wiki/FunctionMultiVersioning, GCC wiki on
+@uref{https://gcc.gnu.org/wiki/FunctionMultiVersioning, GCC wiki on
Function Multiversioning} for more details.
@node Type Traits
implemented in GCC@.
Additional tutorial information is linked to from
-@uref{http://gcc.gnu.org/readings.html}.
+@uref{https://gcc.gnu.org/readings.html}.
@menu
* Contributing:: How to contribute to testing and developing GCC.
For more information, see:
@smallexample
-@uref{http://www.gnu.org/}
-@uref{http://www.gnu.org/gnu/linux-and-gnu.html}
+@uref{https://www.gnu.org/}
+@uref{https://www.gnu.org/gnu/linux-and-gnu.html}
@end smallexample
Some choices depend on the externally determined ABI for the platform
(including standard character encodings) which GCC follows; these are
listed as ``determined by ABI'' below. @xref{Compatibility, , Binary
-Compatibility}, and @uref{http://gcc.gnu.org/readings.html}. Some
+Compatibility}, and @uref{https://gcc.gnu.org/readings.html}. Some
choices are documented in the preprocessor manual.
@xref{Implementation-defined behavior, , Implementation-defined
behavior, cpp, The C Preprocessor}. Some choices are made by the
Some choices depend on the externally determined ABI for the platform
(including standard character encodings) which GCC follows; these are
listed as ``determined by ABI'' below. @xref{Compatibility, , Binary
-Compatibility}, and @uref{http://gcc.gnu.org/readings.html}. Some
+Compatibility}, and @uref{https://gcc.gnu.org/readings.html}. Some
choices are documented in the preprocessor manual.
@xref{Implementation-defined behavior, , Implementation-defined
behavior, cpp, The C Preprocessor}. Some choices are documented in
@c man end
@c man begin COPYRIGHT
Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-@uref{http://fsf.org/}
+@uref{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@display
Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-@uref{http://fsf.org/}
+@uref{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
of the GNU Free Documentation 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. See
-@uref{http://www.gnu.org/copyleft/}.
+@uref{https://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
@c This file is intended to be included in another file.
@display
-Copyright @copyright{} 2007 Free Software Foundation, Inc. @url{http://fsf.org/}
+Copyright @copyright{} 2007 Free Software Foundation, Inc. @url{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
General Public License for more details.
You should have received a copy of the GNU General Public License
-along with this program. If not, see @url{http://www.gnu.org/licenses/}.
+along with this program. If not, see @url{https://www.gnu.org/licenses/}.
@end smallexample
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or school,
if any, to sign a ``copyright disclaimer'' for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
-@url{http://www.gnu.org/licenses/}.
+@url{https://www.gnu.org/licenses/}.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
@end ifnothtml
The latest version of this document is always available at
-@uref{http://gcc.gnu.org/install/,,http://gcc.gnu.org/install/}.
+@uref{https://gcc.gnu.org/install/,,https://gcc.gnu.org/install/}.
It refers to the current development sources, instructions for
specific released versions are included with the sources.
you proceed.
Lists of successful builds for released versions of GCC are
-available at @uref{http://gcc.gnu.org/buildstat.html}.
+available at @uref{https://gcc.gnu.org/buildstat.html}.
These lists are updated as new information becomes available.
The installation procedure itself is broken into five steps.
@cindex Downloading GCC
@cindex Downloading the Source
-GCC is distributed via @uref{http://gcc.gnu.org/git.html,,git} and via
+GCC is distributed via @uref{https://gcc.gnu.org/git.html,,git} and via
HTTPS as tarballs compressed with @command{gzip} or @command{bzip2}.
-Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
+Please refer to the @uref{https://gcc.gnu.org/releases.html,,releases web page}
for information on how to obtain GCC@.
The source distribution includes the C, C++, Objective-C, Fortran,
being used as the target C@tie{} library. This causes float support
functions like @code{__addsf3} to be omitted from @file{libgcc.a} on
the assumption that it will be provided by @file{libm.a}. For more
-technical details, cf. @uref{http://gcc.gnu.org/PR54461,,PR54461}.
+technical details, cf. @uref{https://gcc.gnu.org/PR54461,,PR54461}.
It is not supported for
RTEMS configurations, which currently use newlib. The option is
supported since version 4.7.2 and is the default in 4.8.0 and newer.
Before you install GCC, we encourage you to run the testsuites and to
compare your results with results from a similar configuration that have
been submitted to the
-@uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
+@uref{https://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
Some of these archived results are linked from the build status lists
-at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
+at @uref{https://gcc.gnu.org/buildstat.html}, although not everyone who
reports a successful build runs the testsuites and submits the results.
This step is optional and may require you to download additional software,
but it can give you confidence in your new GCC installation or point out
separately.
Second, you must have the testing tools installed. This includes
-@uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
+@uref{https://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
the DejaGnu site has links to these.
Some optional tests also require Python3 and pytest module.
@samp{WARNING: Couldn't find tool init file} that can be ignored.
If you are testing a cross-compiler, you may want to run the testsuite
-on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
+on a simulator as described at @uref{https://gcc.gnu.org/simtest-howto.html}.
@section How can you run the testsuite on selected tests?
If you are bootstrapping a released version of GCC then please
quickly review the build status page for your release, available from
-@uref{http://gcc.gnu.org/buildstat.html}.
+@uref{https://gcc.gnu.org/buildstat.html}.
If your system is not listed for the version of GCC that you built,
send a note to
@email{gcc@@gcc.gnu.org} indicating
number of platforms.
@item
-The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
+The @uref{https://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
links to GNU Fortran binaries for several platforms.
@end itemize
@anchor{ix86-x-linux}
@heading i?86-*-linux*
As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
-See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
+See @uref{https://gcc.gnu.org/PR10877,,bug 10877} for more information.
If you receive Signal 11 errors when building on GNU/Linux, then it is
possible you have a hardware problem. Further information on this can be
GCC-produced object files into an executable that overflows the TOC@. A fix
for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
available from IBM Customer Support and from its
-@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
+@uref{https://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
website as PTF U455193.
The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
with a segmentation fault when invoked by any version of GCC@. A fix for
APAR IX87327 is available from IBM Customer Support and from its
-@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
+@uref{https://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
The initial assembler shipped with AIX 4.3.0 generates incorrect object
files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
-@uref{http://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
+@uref{https://techsupport.services.ibm.com/,,techsupport.services.ibm.com}
website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
AIX provides National Language Support (NLS)@. Compilers and assemblers
This version of GCC requires at least cctools-590.36. The
cctools-590.36 package referenced from
-@uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
+@uref{https://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
on systems older than 10.3.9 (aka darwin7.9.0).
@html
@c man end
@c man begin AUTHOR
See the Info entry for @command{gcc}, or
-@w{@uref{http://gcc.gnu.org/onlinedocs/gcc/Contributors.html}},
+@w{@uref{https://gcc.gnu.org/onlinedocs/gcc/Contributors.html}},
for contributors to GCC@.
@c man end
@end ignore
bugs and floating-point issues
(mainly but not entirely relating to optional C99 features from
Annexes F and G). See
-@w{@uref{http://gcc.gnu.org/c99status.html}} for more information. The
+@w{@uref{https://gcc.gnu.org/c99status.html}} for more information. The
names @samp{c9x} and @samp{iso9899:199x} are deprecated.
@item c11
over the precise meaning of the sequence point rules in subtle cases.
Links to discussions of the problem, including proposed formal
definitions, may be found on the GCC readings page, at
-@uref{http://gcc.gnu.org/@/readings.html}.
+@uref{https://gcc.gnu.org/@/readings.html}.
This warning is enabled by @option{-Wall} for C and C++.
the DSOs.
An overview of these techniques, their benefits and how to use them
-is at @uref{http://gcc.gnu.org/@/wiki/@/Visibility}.
+is at @uref{https://gcc.gnu.org/@/wiki/@/Visibility}.
@item -fstrict-volatile-bitfields
@opindex fstrict-volatile-bitfields
can use @option{-mgp32} to get 32-bit code instead.
For information about the O64 ABI, see
-@uref{http://gcc.gnu.org/@/projects/@/mipso64-abi.html}.
+@uref{https://gcc.gnu.org/@/projects/@/mipso64-abi.html}.
GCC supports a variant of the o32 ABI in which floating-point registers
are 64 rather than 32 bits wide. You can select this combination with
Graphite is a loop transformation framework based on the polyhedral
model. Graphite stands for Gimple Represented as Polyhedra. The
internals of this infrastructure are documented in
-@w{@uref{http://gcc.gnu.org/wiki/Graphite}}. The passes working on
+@w{@uref{https://gcc.gnu.org/wiki/Graphite}}. The passes working on
this representation are implemented in the various @file{graphite-*}
files.
@end itemize
For further information, see
-@uref{http://gcc.gnu.org/faq.html#support}.
+@uref{https://gcc.gnu.org/faq.html#support}.
This chapter describes the structure of the GCC source tree, and how
GCC is built. The user documentation for building and installing GCC
-is in a separate manual (@uref{http://gcc.gnu.org/install/}), with
+is in a separate manual (@uref{https://gcc.gnu.org/install/}), with
which it is presumed that you are familiar.
@menu
development, drafts of this standard version were referred to as
@dfn{C9X}.) GCC has substantially
complete support for this standard version; see
-@uref{http://gcc.gnu.org/c99status.html} for details. To select this
+@uref{https://gcc.gnu.org/c99status.html} for details. To select this
standard, use @option{-std=c99} or @option{-std=iso9899:1999}.
Errors in the 1999 ISO C standard were corrected in three Technical
For references to Technical Corrigenda, Rationale documents and
information concerning the history of C that is available online, see
-@uref{http://gcc.gnu.org/readings.html}
+@uref{https://gcc.gnu.org/readings.html}
@section C++ Language
@end itemize
For more information concerning the history of Objective-C that is
-available online, see @uref{http://gcc.gnu.org/readings.html}
+available online, see @uref{https://gcc.gnu.org/readings.html}
@section Go Language
The GNU Fortran compiler passes the
@uref{http://www.fortran-2000.com/ArnaudRecipes/fcvs21_f95.html,
NIST Fortran 77 Test Suite}, and produces acceptable results on the
-@uref{http://www.netlib.org/lapack/faq.html#1.21, LAPACK Test Suite}.
+@uref{https://www.netlib.org/lapack/faq.html#1.21, LAPACK Test Suite}.
It also provides respectable performance on
the @uref{https://polyhedron.com/?page_id=175,
Polyhedron Fortran compiler benchmarks} and the
-@uref{http://www.netlib.org/benchmark/livermore,
+@uref{https://www.netlib.org/benchmark/livermore,
Livermore Fortran Kernels test}. It has been used to compile a number of
large real-world programs, including
@uref{http://hirlam.org/, the HARMONIE and HIRLAM weather forecasting code} and
Additionally, the GNU Fortran compilers supports the OpenMP specification
(version 4.5 and partial support of the features of the 5.0 version,
-@url{http://openmp.org/@/openmp-specifications/}).
+@url{https://openmp.org/@/openmp-specifications/}).
There also is support for the OpenACC specification (targeting
-version 2.6, @uref{http://www.openacc.org/}). See
+version 2.6, @uref{https://www.openacc.org/}). See
@uref{https://gcc.gnu.org/wiki/OpenACC} for more information.
@node Fortran 95 status
varying length character strings. While GNU Fortran currently does not
support such strings directly, there exist two Fortran implementations
for them, which work with GNU Fortran. They can be found at
-@uref{http://www.fortran.com/@/iso_varying_string.f95} and at
+@uref{https://www.fortran.com/@/iso_varying_string.f95} and at
@uref{ftp://ftp.nag.co.uk/@/sc22wg5/@/ISO_VARYING_STRING/}.
Deferred-length character strings of Fortran 2003 supports part of
and environment variables that influence run-time behavior.
GNU Fortran strives to be compatible to the
-@uref{http://openmp.org/wp/openmp-specifications/,
+@uref{https://openmp.org/wp/openmp-specifications/,
OpenMP Application Program Interface v4.5}.
To enable the processing of the OpenMP directive @code{!$omp} in
influence run-time behavior.
GNU Fortran strives to be compatible to the
-@uref{http://www.openacc.org/, OpenACC Application Programming
+@uref{https://www.openacc.org/, OpenACC Application Programming
Interface v2.6}.
To enable the processing of the OpenACC directive @code{!$acc} in
below.
For details refer to the actual
-@uref{http://www.openmp.org/wp-content/uploads/openmp-4.5.pdf,
+@uref{https://www.openmp.org/wp-content/uploads/openmp-4.5.pdf,
OpenMP Application Program Interface v4.5} and
@uref{https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5.0.pdf,
OpenMP Application Program Interface v5.0}.
are listed below.
For details refer to the actual
-@uref{http://www.openacc.org/,
+@uref{https://www.openacc.org/,
OpenACC Application Programming Interface v2.6}.
@code{OPENACC} provides the scalar default-integer
the Go programming language. This manual is specifically about
@command{gccgo}. For more information about the Go programming
language in general, including language specifications and standard
-package documentation, see @uref{http://golang.org/}.
+package documentation, see @uref{https://golang.org/}.
@menu
* Copying:: The GNU General Public License.
This information is provided largely for documentation purposes. For
ordinary use it is best to build programs with the go tool and then
use @code{import "C"}, as described at
-@url{http://golang.org/cmd/cgo}.
+@url{https://golang.org/cmd/cgo}.
@menu
* C Type Interoperability:: How C and Go types match up.
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
-This document describes libgccjit@footnote{http://gcc.gnu.org/wiki/JIT}, an API
+This document describes libgccjit@footnote{https://gcc.gnu.org/wiki/JIT}, an API
for embedding GCC inside programs and libraries.
There are actually two APIs for the library:
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Tutorial::
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Tutorial part 1; “Hello world”: Tutorial part 1 “Hello world”.
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 2 Creating a trivial machine code function,Tutorial part 3 Loops and variables,Tutorial part 1 “Hello world”,Tutorial
@anchor{intro/tutorial02 doc}@anchor{6}@anchor{intro/tutorial02 tutorial-part-2-creating-a-trivial-machine-code-function}@anchor{7}
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 3 Loops and variables,Tutorial part 4 Adding JIT-compilation to a toy interpreter,Tutorial part 2 Creating a trivial machine code function,Tutorial
@anchor{intro/tutorial03 doc}@anchor{21}@anchor{intro/tutorial03 tutorial-part-3-loops-and-variables}@anchor{22}
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 4 Adding JIT-compilation to a toy interpreter,Tutorial part 5 Implementing an Ahead-of-Time compiler,Tutorial part 3 Loops and variables,Tutorial
@anchor{intro/tutorial04 doc}@anchor{35}@anchor{intro/tutorial04 tutorial-part-4-adding-jit-compilation-to-a-toy-interpreter}@anchor{36}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 5 Implementing an Ahead-of-Time compiler,,Tutorial part 4 Adding JIT-compilation to a toy interpreter,Tutorial
@anchor{intro/tutorial05 doc}@anchor{48}@anchor{intro/tutorial05 tutorial-part-5-implementing-an-ahead-of-time-compiler}@anchor{49}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Topic Reference,C++ bindings for libgccjit,Tutorial,Top
@anchor{topics/index doc}@anchor{4f}@anchor{topics/index topic-reference}@anchor{50}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Compilation contexts::
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Objects,Types,Compilation contexts,Topic Reference
@anchor{topics/objects doc}@anchor{76}@anchor{topics/objects objects}@anchor{77}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Types,Expressions,Objects,Topic Reference
@anchor{topics/types doc}@anchor{79}@anchor{topics/types types}@anchor{7a}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Expressions,Creating and using functions,Types,Topic Reference
@anchor{topics/expressions doc}@anchor{96}@anchor{topics/expressions expressions}@anchor{97}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Creating and using functions,Function pointers<2>,Expressions,Topic Reference
@anchor{topics/functions doc}@anchor{d5}@anchor{topics/functions creating-and-using-functions}@anchor{d6}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Function pointers<2>,Source Locations,Creating and using functions,Topic Reference
@anchor{topics/function-pointers doc}@anchor{f2}@anchor{topics/function-pointers function-pointers}@anchor{f3}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Source Locations,Compiling a context,Function pointers<2>,Topic Reference
@anchor{topics/locations doc}@anchor{f5}@anchor{topics/locations source-locations}@anchor{f6}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Compiling a context,ABI and API compatibility,Source Locations,Topic Reference
@anchor{topics/compilation doc}@anchor{f8}@anchor{topics/compilation compiling-a-context}@anchor{f9}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node ABI and API compatibility,Performance,Compiling a context,Topic Reference
@anchor{topics/compatibility doc}@anchor{101}@anchor{topics/compatibility abi-and-api-compatibility}@anchor{102}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Performance,Using Assembly Language with libgccjit,ABI and API compatibility,Topic Reference
@anchor{topics/performance doc}@anchor{12c}@anchor{topics/performance performance}@anchor{12d}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Using Assembly Language with libgccjit,,Performance,Topic Reference
@anchor{topics/asm doc}@anchor{131}@anchor{topics/asm using-assembly-language-with-libgccjit}@anchor{132}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node C++ bindings for libgccjit,Internals,Topic Reference,Top
@anchor{cp/index doc}@anchor{135}@anchor{cp/index c-bindings-for-libgccjit}@anchor{136}
This document describes the C++ bindings to
-libgccjit@footnote{http://gcc.gnu.org/wiki/JIT}, an API for embedding GCC
+libgccjit@footnote{https://gcc.gnu.org/wiki/JIT}, an API for embedding GCC
inside programs and libraries.
The C++ bindings consist of a single header file @code{libgccjit++.h}.
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Tutorial: Tutorial<2>.
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Tutorial part 1; “Hello world”: Tutorial part 1 “Hello world”<2>.
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit++.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 2 Creating a trivial machine code function<2>,Tutorial part 3 Loops and variables<2>,Tutorial part 1 “Hello world”<2>,Tutorial<2>
@anchor{cp/intro/tutorial02 doc}@anchor{13b}@anchor{cp/intro/tutorial02 tutorial-part-2-creating-a-trivial-machine-code-function}@anchor{13c}
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit++.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 3 Loops and variables<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2>,Tutorial part 2 Creating a trivial machine code function<2>,Tutorial<2>
@anchor{cp/intro/tutorial03 doc}@anchor{14c}@anchor{cp/intro/tutorial03 tutorial-part-3-loops-and-variables}@anchor{14d}
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
-<http://www.gnu.org/licenses/>. */
+<https://www.gnu.org/licenses/>. */
#include <libgccjit++.h>
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Tutorial part 4 Adding JIT-compilation to a toy interpreter<2>,,Tutorial part 3 Loops and variables<2>,Tutorial<2>
@anchor{cp/intro/tutorial04 doc}@anchor{15e}@anchor{cp/intro/tutorial04 tutorial-part-4-adding-jit-compilation-to-a-toy-interpreter}@anchor{15f}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Topic Reference<2>,,Tutorial<2>,C++ bindings for libgccjit
@anchor{cp/topics/index doc}@anchor{16f}@anchor{cp/topics/index topic-reference}@anchor{170}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@menu
* Compilation contexts: Compilation contexts<2>.
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Objects<2>,Types<2>,Compilation contexts<2>,Topic Reference<2>
@anchor{cp/topics/objects doc}@anchor{1ab}@anchor{cp/topics/objects objects}@anchor{1ac}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Types<2>,Expressions<2>,Objects<2>,Topic Reference<2>
@anchor{cp/topics/types doc}@anchor{1b7}@anchor{cp/topics/types types}@anchor{1b8}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Expressions<2>,Creating and using functions<2>,Types<2>,Topic Reference<2>
@anchor{cp/topics/expressions doc}@anchor{1f6}@anchor{cp/topics/expressions expressions}@anchor{1f7}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Creating and using functions<2>,Source Locations<2>,Expressions<2>,Topic Reference<2>
@anchor{cp/topics/functions doc}@anchor{2fb}@anchor{cp/topics/functions creating-and-using-functions}@anchor{2fc}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Source Locations<2>,Compiling a context<2>,Creating and using functions<2>,Topic Reference<2>
@anchor{cp/topics/locations doc}@anchor{33e}@anchor{cp/topics/locations source-locations}@anchor{33f}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Compiling a context<2>,Using Assembly Language with libgccjit++,Source Locations<2>,Topic Reference<2>
@anchor{cp/topics/compilation doc}@anchor{347}@anchor{cp/topics/compilation compiling-a-context}@anchor{348}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Using Assembly Language with libgccjit++,,Compiling a context<2>,Topic Reference<2>
@anchor{cp/topics/asm doc}@anchor{352}@anchor{cp/topics/asm using-assembly-language-with-libgccjit}@anchor{353}
@c
@c You should have received a copy of the GNU General Public License
@c along with this program. If not, see
-@c <http://www.gnu.org/licenses/>.
+@c <https://www.gnu.org/licenses/>.
@node Internals,Indices and tables,C++ bindings for libgccjit,Top
@anchor{internals/index doc}@anchor{382}@anchor{internals/index internals}@anchor{383}
@geindex environment variable; RUN_UNDER_VALGRIND
@code{RUN_UNDER_VALGRIND} is present in the
environment (with any value). If it is present, it runs the test client
-code under valgrind@footnote{http://valgrind.org},
+code under valgrind@footnote{https://valgrind.org},
specifcally, the default
-memcheck@footnote{http://valgrind.org/docs/manual/mc-manual.html}
+memcheck@footnote{https://valgrind.org/docs/manual/mc-manual.html}
tool with
---leak-check=full@footnote{http://valgrind.org/docs/manual/mc-manual.html#opt.leak-check}.
+--leak-check=full@footnote{https://valgrind.org/docs/manual/mc-manual.html#opt.leak-check}.
It automatically parses the output from valgrind, injecting XFAIL results if
any issues are found, or PASS results if the output is clean. The output
Typically a patch that touches the .rst documentation will also need the
texinfo to be regenerated. You can do this with
-Sphinx 1.0@footnote{http://sphinx-doc.org/} or later by
+Sphinx 1.0@footnote{https://sphinx-doc.org/} or later by
running @code{make texinfo} within @code{SRCDIR/gcc/jit/docs}. Don’t do this
within the patch sent to the mailing list; it can often be relatively
large and inconsequential (e.g. anchor renumbering), rather like generated
@c The Sphinx C domain appears to lack explicit support for enum values,
@c so I've been using :c:macro: for them.
@c
-@c See http://sphinx-doc.org/domains.html#the-c-domain
+@c See https://sphinx-doc.org/domains.html#the-c-domain
@node Index,,Indices and tables,Top
@unnumbered Index
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
C++ bindings for libgccjit
==========================
This document describes the C++ bindings to
-`libgccjit <http://gcc.gnu.org/wiki/JIT>`_, an API for embedding GCC
+`libgccjit <https://gcc.gnu.org/wiki/JIT>`_, an API for embedding GCC
inside programs and libraries.
The C++ bindings consist of a single header file ``libgccjit++.h``.
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Tutorial
========
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Topic Reference
===============
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: cpp
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
libgccjit
=========
-This document describes `libgccjit <http://gcc.gnu.org/wiki/JIT>`_, an API
+This document describes `libgccjit <https://gcc.gnu.org/wiki/JIT>`_, an API
for embedding GCC inside programs and libraries.
There are actually two APIs for the library:
The Sphinx C domain appears to lack explicit support for enum values,
so I've been using :c:macro: for them.
- See http://sphinx-doc.org/domains.html#the-c-domain
+ See https://sphinx-doc.org/domains.html#the-c-domain
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Internals
=========
The jit testsuite detects if :envvar:`RUN_UNDER_VALGRIND` is present in the
environment (with any value). If it is present, it runs the test client
-code under `valgrind <http://valgrind.org>`_,
+code under `valgrind <https://valgrind.org>`_,
specifcally, the default
-`memcheck <http://valgrind.org/docs/manual/mc-manual.html>`_
+`memcheck <https://valgrind.org/docs/manual/mc-manual.html>`_
tool with
`--leak-check=full
-<http://valgrind.org/docs/manual/mc-manual.html#opt.leak-check>`_.
+<https://valgrind.org/docs/manual/mc-manual.html#opt.leak-check>`_.
It automatically parses the output from valgrind, injecting XFAIL results if
any issues are found, or PASS results if the output is clean. The output
Typically a patch that touches the .rst documentation will also need the
texinfo to be regenerated. You can do this with
-`Sphinx 1.0 <http://sphinx-doc.org/>`_ or later by
+`Sphinx 1.0 <https://sphinx-doc.org/>`_ or later by
running ``make texinfo`` within ``SRCDIR/gcc/jit/docs``. Don't do this
within the patch sent to the mailing list; it can often be relatively
large and inconsequential (e.g. anchor renumbering), rather like generated
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Tutorial
========
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Tutorial part 3: Loops and variables
------------------------------------
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Tutorial part 4: Adding JIT-compilation to a toy interpreter
------------------------------------------------------------
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Tutorial part 5: Implementing an Ahead-of-Time compiler
-------------------------------------------------------
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
Topic Reference
===============
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
You should have received a copy of the GNU General Public License
along with this program. If not, see
- <http://www.gnu.org/licenses/>.
+ <https://www.gnu.org/licenses/>.
.. default-domain:: c
projects / test_jj.git / commitdiff