Lines Matching full:that

15 The set of runtime conventions followed by all of the tools that deal
23 A compiler conforms to an ABI if it generates code that follows all of
24 the specifications enumerated by that ABI@.
25 A library conforms to an ABI if it is implemented according to that ABI@.
26 An application conforms to an ABI if it is built using tools that conform
27 to that ABI and does not contain source code that specifically changes
31 Calling conventions are a subset of an ABI that specify of how arguments
35 Different sets of tools are interoperable if they generate files that
51 The features that are not covered by an ABI generally affect how a
92 Some GCC compilation options cause the compiler to generate code that
94 different program behavior for implementation-defined features that are
96 other compilers that do not follow the platform's default ABI or the
100 Most platforms have a well-defined ABI that covers C code, but ABIs
101 that cover C++ functionality are not yet common.
104 written, vendor-neutral C++ ABI that was designed to be specific to
105 64-bit Itanium but also includes generic specifications that apply to
109 We have tried hard to provide a stable ABI that will be compatible with
110 future GCC releases, but it is possible that we will encounter problems
111 that make this difficult.  Such problems could include different
114 GCC's @code{-Wabi} switch warns when G++ generates code that is
121 of that library are interoperable if one follows the de-facto ABI of the
123 that conform to the same ABI for C++ compiler and runtime support.
126 implementations of the Standard C++ Library that they normally use do not
140 Similarly, compiling code with G++ that must use a C++ library other
142 files for that other library.
145 C++ library is to use a C++ driver that specifies that C++ library by
151 to do the final link using a C++ driver that uses that library by default,
152 it is necessary to tell @command{g++} the location and name of that